-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Compatibility with [email protected] #1945
Comments
I see that the API has changed significantly - https://github.com/webpack-contrib/style-loader/releases/tag/v1.0.0. |
We use only the
|
I created PRs in ckeditor5, ckeditor5-build-* and ckeditor5-dev that migrate the entire project to style-loader v1.0.0. Root PR. |
It seems to work replacing |
Other: Bumped style-loader to v1.0.0. Aligned the webpack config to the new loader API. See ckeditor/ckeditor5#1945.
Other: Bumped style-loader to v1.0.0. Aligned configurations and documentation to the new loader API. Closes #1945.
Other: Bumped style-loader to v1.0.0. Aligned the webpack config to the new loader API. See ckeditor/ckeditor5#1945.
Other: Bumped style-loader to v1.0.0. Aligned the webpack config to the new loader API. See ckeditor/ckeditor5#1945.
Other: Bumped style-loader to v1.0.0. Aligned the webpack config to the new loader API. See ckeditor/ckeditor5#1945.
Other: Bumped style-loader to v1.0.0. Aligned the webpack config to the new loader API. See ckeditor/ckeditor5#1945.
Other: Bumped style-loader to v1.0.0. Aligned the webpack config to the new loader API. See ckeditor/ckeditor5#1945.
Other: Bumped style-loader to v1.0.0. Aligned the webpack config to the new loader API. See ckeditor/ckeditor5#1945.
When you're following our quick start guide, where we explain to install
style-loader
from npm, you end up with this error:Apparently, the new version of style-loader (so far, we've been using 0.23.0) changed something in its configuration. We've got to look into that. For now, I'll make a PR to add a version specifier to
npm i
call.The text was updated successfully, but these errors were encountered: