Skip to content
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

Document webpack change: feat: resolve style fields in package json #6909

Closed
webpack-bot opened this issue Jun 14, 2023 · 2 comments · Fixed by #6919
Closed

Document webpack change: feat: resolve style fields in package json #6909

webpack-bot opened this issue Jun 14, 2023 · 2 comments · Fixed by #6919
Assignees

Comments

@webpack-bot
Copy link

A pull request by @burhanuday was merged and maintainers requested a documentation change.

See pull request: webpack/webpack#17346


Part of webpack/webpack#14893

supports style resolution in package.json and test it + test support loader usage

Summary

🤖 Generated by Copilot at 15e1e2a

This pull request improves the support for style modules and assets in webpack by adding new resolution properties and updating the test cases. It modifies the lib/config/defaults.js file to define and apply the new properties, and the test/configCases/css/css-import files to import and test different style modules.

Details

🤖 Generated by Copilot at 15e1e2a

  • Add styleResolutionDefaults object to define common properties for resolving style modules (link)
  • Test the cascading effect of css imports by importing style-import.css in style.css (link)
@TheLarkInn
Copy link
Member

I'll let you use best judgement here, I think the key detail to document with this feature is that using experiments.css means that styles will be added as a resolvable main field.

If possible it would be fantastic to leverage the test case examples to call out examples in the docs. <3 @burhanuday I'd appreciate if you could assist if @chenxsan or another contributor needs assistance.

@burhanuday
Copy link
Member

I'll take up the documentation effort for this

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 a pull request may close this issue.

3 participants