-
Notifications
You must be signed in to change notification settings - Fork 130
Closed
4 / 44 of 4 issues completedClosed
4 / 44 of 4 issues completed
Copy link
Description
After following all update steps described in the 16.2.0 CHANGELOG i get the following error when trying to precompile the assets:
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration.entry should be one of these:
function | object { <key>: non-empty string | [non-empty string] } | non-empty string | [non-empty string]
-> The entry point(s) of the compilation.
Details:
* configuration.entry['pageflow-scrolled/widgets/iconInlineFileRights'] should be a string.
-> The string is resolved to a module which is loaded upon startup.
* configuration.entry['pageflow-scrolled/widgets/iconInlineFileRights'] should be an array:
[non-empty string]
-> A non-empty array of non-empty strings
* configuration.entry['pageflow-scrolled/widgets/iconInlineFileRights'] should be one of these:
[non-empty string]
-> All modules are loaded upon startup. The last one is exported.
* configuration.entry['pageflow-scrolled/widgets/iconInlineFileRights'] should be one of these:
non-empty string | [non-empty string]
-> An entry point with name
* configuration.entry['pageflow-scrolled/widgets/textInlineFileRights'] should be a string.
-> The string is resolved to a module which is loaded upon startup.
* configuration.entry['pageflow-scrolled/widgets/textInlineFileRights'] should be an array:
[non-empty string]
-> A non-empty array of non-empty strings
* configuration.entry['pageflow-scrolled/widgets/textInlineFileRights'] should be one of these:
[non-empty string]
-> All modules are loaded upon startup. The last one is exported.
* configuration.entry['pageflow-scrolled/widgets/textInlineFileRights'] should be one of these:
non-empty string | [non-empty string]
-> An entry point with name
the paths mentioned here are exactly the new imports coming from pageflow-scrolled/widgets-server
. Is there maybe a problem with a webpack4 vs webpack5 conflict?
Here is an archive with my config files (Gemfile, Gemfile.lock, package.json, yarn.lock, webpacker.yml)
Thanks in advance and best regards
Ronald
Sub-issues
Metadata
Metadata
Assignees
Labels
No labels