-
-
Notifications
You must be signed in to change notification settings - Fork 199
updating css-loader dep and ts-loader dev dep #440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| "stylus": "^0.54.5", | ||
| "stylus-loader": "^3.0.2", | ||
| "ts-loader": "^4.3.0", | ||
| "ts-loader": "^5.3.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is in devDependencies, so it really just means that we test against this version - the user can install something lower, but they will get a warning. We could also set this to ^5.0.0, which would mean we would test against 5.0.0 in one our test suites. When the user needs to install this, they would be give the command yarn add ts-loader ^5.0.0, but that should install the latest version anyways.
This is needed for the latest version of css-loader, which does not handle this
e9dd099 to
241e8ae
Compare
|
This has one minor failing test, but is otherwise ready for review |
... and also that, due to some old bad code, the .map files were not being removed correctly for style entries in production.
| // remove the output file | ||
| delete compilation.assets[filename]; | ||
| // remove the file, so that it does not dump in the manifest | ||
| chunk.files.splice(chunk.files.indexOf(filename), 1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chunk.files.indexOf(filename) could be i instead
Fixes #438 and fixes #431 and I believe fixes #432
This PR is more interesting than I expected! The latest version of
css-loader(1.0) does not have theminimizeoption. Even though (until now) the older version was locked on ourpackage.json, it may have been possible for users to be using a new version (I believe that should not be possible, but node deps can do strange things).