Move webpack-dev-middleware from custom to latest#383
Merged
Mortaro merged 1 commit intonullstack:nextfrom Aug 29, 2023
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Having it as a git dependency meant that at every install would install their devDeps and built on-the-fly (with
preparescript).On another way, Yarn deprecated running the
prepareand something like that was only reimplemented on v2+ (which can be read-on in issues like those: yarnpkg/yarn#7910 and yarnpkg/berry#957).Thinking on improving support I thought the best would be to build the package on git itself (simulating the npm registry).
In the end we concluded that using the package custom version wasn't being worth it, then here it is, this PR is just to invest on the latest original package version 🚀
webpack-dev-middlewarereleases