blog: webpack 5.105 #7763
blog: webpack 5.105 #7763
Conversation
|
@bjohansebas is attempting to deploy a commit to the OpenJS Foundation Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
alexander-akait
left a comment
alexander-akait
left a comment
There was a problem hiding this comment.
Yeah, good job, we are planning to make a new release on Monday, do you want to improve something else here?
| "import/no-amd": "off", | ||
| "import/extensions": "off", | ||
| "import/default": "off", | ||
| "unicorn/relative-url-style": "off", |
There was a problem hiding this comment.
Better to disable this rule directly in mdx, you can find an example in our code base, otherwise we will disable a lot of rules in future due, or disable this rules specific for this file, but using a comment is better
I’ll take a look at it on Saturday. Let me know if there’s any other minor functionality that’s being added so I can include it as well. |
4 participants
Summary
As I was saying on Discord, I want to start helping create blogs about the changes between minor versions, also as a way to support the project's marketing.
Reference for the changes coming in release webpack/webpack#20256, webpack/webpack#20353
Cc: @webpack/tsc @webpack/core-wg
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
If relevant, what needs to be documented once your changes are merged or what have you already documented?