Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today, an import like
in the run-time code (everything in
src/
) makesnpm run build
fail like this:With Userscripter 3.0.0, it instead fails with an unintelligible wall of text containing, among others, these errors:
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Critical dependency: the request of a dependency is an expression
Module not found: Error: Can't resolve 'fsevents' in '/home/alling/dev/better-sweclockers/node_modules/chokidar/lib'
System.import() is deprecated and will be removed soon. Use import() instead.
require.extensions is not supported by webpack. Use a loader instead.
Can't import the named export 'RawSource' from non EcmaScript module (only default export is available)
That in itself is of course a downgrade, but I want to upgrade Userscripter as new versions are released unless there is a compelling reason not to.