Skip to content

dependencies: update to webpack 5, patch karma-webpack#1119

Merged
sschmidTU merged 6 commits into
developfrom
feat/webpack5
Jan 7, 2022
Merged

dependencies: update to webpack 5, patch karma-webpack#1119
sschmidTU merged 6 commits into
developfrom
feat/webpack5

Conversation

@sschmidTU

Copy link
Copy Markdown
Contributor

Includes Npm updates from #1105, which was first merged to feat/webpack5.
Karma-webpack 5.0 needs some patches to work correctly with Windows and MacOS file paths, which are now complete.

rvilarl and others added 4 commits December 16, 2021 19:43
…6, etc. (#1105)

this needs an upcoming fix to karma-webpack 5.0 in a further commit, see here:
#1105 (comment)

* npm-upgrade

* timeout increased

* process.env is not defined

* generateImages_browserles migrated to mjs

* review comments

* npm-upgrade

(cherry picked from commit 801b44a)
@sschmidTU sschmidTU self-assigned this Jan 7, 2022
sschmidTU added 2 commits January 8, 2022 00:00
This reverts commit 5fd2b5a.

turns out the problem is in webpack (bundling),
not in karma-webpack.
and it looks like it's not simple to fix:
webpack/webpack#12759

So we'll have to give up windows multiple drive support for now,
this is the easiest option,
as it works on MacOS (with patch) and Linux now.
@sschmidTU

Copy link
Copy Markdown
Contributor Author

Turns out the npm test error in Windows comes from webpack, not directly from karma-webpack,
and it looks like it's not simple to fix:
webpack/webpack#12759

So we'll have to give up windows multiple drive support for now and just merge this,
this is the easiest option,
as it works on MacOS (with patch) and Linux now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants