chore(deps): update all non-major dependencies#459
Merged
Shinigami92 merged 1 commit intomainfrom Feb 10, 2022
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## main #459 +/- ##
==========================================
- Coverage 99.32% 99.32% -0.01%
==========================================
Files 1920 1920
Lines 174272 174272
Branches 893 893
==========================================
- Hits 173100 173099 -1
- Misses 1116 1117 +1
Partials 56 56
|
ST-DDT
previously approved these changes
Feb 10, 2022
33a3912 to
8a61638
Compare
ST-DDT
approved these changes
Feb 10, 2022
Shinigami92
approved these changes
Feb 10, 2022
demipel8
pushed a commit
to demipel8/faker
that referenced
this pull request
Mar 11, 2022
Co-authored-by: Renovate Bot <bot@renovateapp.com>
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
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:
~2.4.3->~2.4.4~0.14.20->~0.14.21~37.8.0->~37.8.26.30.0->6.30.1~2.7.13->~2.8.0Release Notes
evanw/esbuild
v0.14.21Compare Source
Handle an additional
browsermap edge case (#2001, #2002)There is a community convention around the
browserfield inpackage.jsonthat allows remapping import paths within a package when the package is bundled for use within a browser. There isn't a rigorous definition of how it's supposed to work and every bundler implements it differently. The approach esbuild uses is to try to be "maximally compatible" in that if at least one bundler exhibits a particular behavior regarding thebrowsermap that allows a mapping to work, then esbuild also attempts to make that work.I have a collection of test cases for this going here: https://github.com/evanw/package-json-browser-tests. However, I was missing test coverage for the edge case where a package path import in a subdirectory of the package could potentially match a remapping. The "maximally compatible" approach means replicating bugs in Browserify's implementation of the feature where package paths are mistaken for relative paths and are still remapped. Here's a specific example of an edge case that's now handled:
entry.js:node_modules/pkg/package.json:{ "browser": { "./sub": "./sub/foo.js", "./sub/sub": "./sub/bar.js" } }node_modules/pkg/sub/foo.js:node_modules/pkg/sub/bar.js:The import path
subinrequire('sub')is mistaken for a relative path by Browserify due to a bug in Browserify, so Browserify treats it as if it were./subinstead. This is a Browserify-specific behavior and currently doesn't happen in any other bundler (except for esbuild, which attempts to replicate Browserify's bug).Previously esbuild was incorrectly resolving
./subrelative to the top-level package directory instead of to the subdirectory in this case, which meant./subwas incorrectly matching"./sub": "./sub/foo.js"instead of"./sub/sub": "./sub/bar.js". This has been fixed so esbuild can now emulate Browserify's bug correctly in this edge case.Support for esbuild with Linux on RISC-V 64bit (#2000)
With this release, esbuild now has a published binary executable for the RISC-V 64bit architecture in the
esbuild-linux-riscv64npm package. This change was contributed by @piggynl.gajus/eslint-plugin-jsdoc
v37.8.2Compare Source
Bug Fixes
empty-tags: prevent tag content forinterfacein Closure mode (1b3212f)v37.8.1Compare Source
Bug Fixes
valid-types: allow dropping oftypedefname and/or type by TypeScript (8847608)pnpm/pnpm
v6.30.1Patch Changes
This fixes an issue introduced in pnpm v6.30.0.
When a package is not linked to
node_modules, no info message should be printed about it being "relinked" from the store #4314.vitejs/vite
v2.8.0Compare Source
Reduced Footprint
Vite 2.8.0 is almost 1/4 of the 2.7.0 publish size, and the install size has been reduced by 35%. See this thread about each change that reduced Vite's footprint.
Default preview port
New default port for
vite previewis 4173 (avoid conflicts in MacOS that took over the 5000 port)Workers using standard syntax
Workers are detected and bundled when using
new URL('path', import.meta.url), replacing the need for the?workersuffix and aligning Vite with standard patterns. See #6356. Instead ofit is now recommended to use
Configuring Workers Bundling
New
workerconfig field adding support for Workerformat,pluginsand,rollupOptions. See #6351worker.format: 'es' | 'iife'Output format for worker bundle (default:
iife).worker.plugins: (Plugin | Plugin[])[]Vite plugins that apply to worker bundle.
worker.rollupOptions:RollupOptionsRollup options to build worker bundle.
The worker plugins pipeline isn't shared with the main Vite pipeline, there may be plugins that shouldn't be applied to Workers. If a plugin must be applied to both the main build and the worker build, you need to add a plugin in the main
pluginsarray and another one in theworker.pluginsconfig.Raw Glob Imports
Glob imports now support the
rawmodifier (that works in the same way as the?rawsuffix in regular imports). Vite is going to gradually migrate to the new standardassertsyntax instead of using custom URL suffixes where possible.server.headersconfig option allowing configuration of response headers in dev mode.Bug Fixes
dotenvwhen specifically scoped (#6682) (c2f0021)tryNodeResolveon absolute paths (#6488) (f346d89)vite:ssr-require-hookafter user plugins (#6306) (d856c4b)hires: truefor SSR require hook source map (#6310) (0ebeb98)Features
searchForWorkspaceRoot(#6270) (0e164f8)error.locback to original source (#5467) (65cd44d)Beta Changelogs
2.8.0-beta.7 (2022-02-08)
See 2.8.0-beta.7 changelog
2.8.0-beta.6 (2022-02-07)
See 2.8.0-beta.6 changelog
2.8.0-beta.5 (2022-02-02)
See 2.8.0-beta.5 changelog
2.8.0-beta.4 (2022-01-31)
See 2.8.0-beta.4 changelog
2.8.0-beta.3 (2022-01-18)
See 2.8.0-beta.3 changelog
2.8.0-beta.2 (2022-01-13)
2.8.0-beta.2 changelog
2.8.0-beta.1 (2022-01-06)
See 2.8.0-beta.1 changelog
2.8.0-beta.0 (2022-01-05)
See 2.8.0-beta.0 changelog
2.7.9 (2021-12-28)
2.7.8 (2021-12-28)
Bug Fixes
2.7.7 (2021-12-26)
Bug Fixes
2.7.6 (2021-12-22)
Bug Fixes
2.7.5 (2021-12-21)
Bug Fixes
2.7.4 (2021-12-20)
Bug Fixes
ssrTransformfunction argument destructure (#6171) (2762a0e)2.7.3 (2021-12-16)
Bug Fixes
2.7.2 (2021-12-13)
Bug Fixes
2.7.1 (2021-12-07)
Bug Fixes
ssrTransformhandling for empty ArrayPattern (#5988) (79aa687)Configuration
📅 Schedule: "before 2am" (UTC).
🚦 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.