build: update all non-major dependencies #21231
Merged
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.
This PR contains the following updates:
4.28.0->4.28.14.28.0->4.28.10.12.11->0.12.121.6.1->1.6.25.40.0->5.41.0Release Notes
typescript-eslint/typescript-eslint
v4.28.1Compare Source
Note: Version bump only for package @typescript-eslint/parser
evanw/esbuild
v0.12.12Compare Source
Fix
fileloader import paths when subdirectories are present (#1044)Using the
fileloader for a file type causes importing affected files to copy the file into the output directory and to embed the path to the copied file into the code that imported it. However, esbuild previously always embedded the path relative to the output directory itself. This is problematic when the importing code is generated within a subdirectory inside the output directory, since then the relative path is wrong. For example:This is output from the previous version of esbuild. The above asset reference in
out/example/entry.cssis wrong. The path should start with../because the two files are in different directories.With this release, the asset references present in output files will now be the full relative path from the output file to the asset, so imports should now work correctly when the entry point is in a subdirectory within the output directory. This change affects asset reference paths in both CSS and JS output files.
Note that if you want asset reference paths to be independent of the subdirectory in which they reside, you can use the
--public-pathsetting to provide the common path that all asset reference paths should be constructed relative to. Specifically--public-path=.should bring back the old problematic behavior in case you need it.Add support for
[dir]in--asset-names(#1196)You can now use path templates such as
--asset-names=[dir]/[name]-[hash]to copy the input directory structure of your asset files (i.e. input files loaded with thefileloader) to the output directory. Here's an example:webpack-contrib/mini-css-extract-plugin
v1.6.2Compare Source
webpack/webpack
v5.41.0Compare Source
Features
cache.idleTimeoutAfterLargeChangesto control thatBugfixes
Experiments
experiments.outputModule: true)output.library.type: "module": very basic support, no live bindings, unnecessary runtime codeoutput.chunkLoading: "import"output.chunkFormat: "module"externalsType: "module"generates nowimport * as X from "..."(in a module) orimport("...")(in a script)import { createRequire } from "module"in a modulenew Workeretc. sets `type: "module"Configuration
📅 Schedule: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.