chore(deps): update non-major #108
Open
+1,057
−651
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/non-major
branch
from
6d7d06b
to
4c79a34
Compare
renovate
bot
changed the title
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
|
renovate
bot
force-pushed
the
renovate/non-major
branch
9 times, most recently
from
5f4bbf9
to
371a96a
Compare
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
renovate
bot
force-pushed
the
renovate/non-major
branch
10 times, most recently
from
1734eb2
to
ba0ada9
Compare
renovate
bot
force-pushed
the
renovate/non-major
branch
4 times, most recently
from
e773740
to
3caf400
Compare
renovate
bot
force-pushed
the
renovate/non-major
branch
3 times, most recently
from
5cad934
to
029478a
Compare
renovate
bot
force-pushed
the
renovate/non-major
branch
2 times, most recently
from
9be63de
to
9d30e58
Compare
renovate
bot
force-pushed
the
renovate/non-major
branch
from
9d30e58
to
3acd101
Compare
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:
^3.0.0->^3.2.0^6.8.18->^6.10.0^4.1.7->^4.1.8^2.1.13->^2.5.0^4.17.4->^4.17.6^7.11.0->^7.15.0^7.11.0->^7.15.0^4.3.0->^4.3.1^0.21.4->^0.22.0^6.8.0->^6.9.0^7.34.2->^7.34.3^3.2.5->^3.3.2^5.2.12->^5.3.2Release Notes
sanity-io/icons (@sanity/icons)
v3.2.0Compare Source
Features
add-documenticon (18f2aa6)v3.1.0Compare Source
Features
unlinkicon (bf48c21)sanity-io/pkg-utils (@sanity/pkg-utils)
v6.10.0Compare Source
Features
rollup:react-compilertask (#963) (1002fac)v6.9.3Compare Source
Bug Fixes
v6.9.2Compare Source
Bug Fixes
v6.9.1Compare Source
Bug Fixes
v6.9.0Compare Source
Features
Bug Fixes
v6.8.19Compare Source
Bug Fixes
sanity-io/semantic-release-preset (@sanity/semantic-release-preset)
v4.1.8Compare Source
Bug Fixes
sanity-io/ui (@sanity/ui)
v2.5.0Compare Source
Features
v2.4.0Compare Source
Features
v2.3.6Compare Source
Bug Fixes
v2.3.5Compare Source
Bug Fixes
v2.3.4Compare Source
Bug Fixes
selectedproperty onMenuButton(eae34c1)v2.3.3Compare Source
Bug Fixes
v2.3.2Compare Source
Bug Fixes
v2.3.1Compare Source
Bug Fixes
v2.3.0Compare Source
Features
useForwardedRef(#1324) (62146b6)v2.2.0Compare Source
Features
mutedproperty (f70bff6)v2.1.14Compare Source
Bug Fixes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.15.0Compare Source
🚀 Features
eslint-plugin: [array-type] detect
Readonly<string[]>caseeslint-plugin: back-port new rules around empty object types from v8
🩹 Fixes
disable
EXPERIMENTAL_useProjectServiceindisabled-type-checkedshared configeslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any
eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.14.1Compare Source
🩹 Fixes
eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types
eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.14.0Compare Source
🚀 Features
🩹 Fixes
eslint-plugin: [no-extraneous-class] handle abstract members
eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types
eslint-plugin: [no-invalid-this] support AccessorProperty
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.13.1Compare Source
🩹 Fixes
eslint-plugin: [prefer-readonly] refine report locations
eslint-plugin: [return-await] support explicit resource management
eslint-plugin: [no-unsafe-member-access] differentiate a types-error any from a true any
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.13.0Compare Source
🚀 Features
typescript-estree: require
import = require()argument to be a string literaltypescript-estree: forbid
.body,.async,.generatorondeclare functioneslint-plugin: [no-dynamic-delete] allow all string literals as index
🩹 Fixes
ast-spec: function-call-like callee should be Expression not LeftHandSideExpression
scope-manager: handle index signature in class
eslint-plugin: [init-declarations] refine report locations
eslint-plugin: [no-base-to-string] make error message more nuanced
eslint-plugin: [no-unsafe-assignment] be more specific about error types
eslint-plugin: [no-magic-numbers] fix implementation of the
ignoreoption❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.12.0Compare Source
🚀 Features
eslint-plugin: [no-useless-template-literals] rename to
no-useless-template-expression(deprecateno-useless-template-literals)rule-tester: check for parsing errors in suggestion fixes
rule-tester: port
checkDuplicateTestCasesfrom ESLinteslint-plugin: [no-floating-promises] add option 'allowForKnownSafePromises'
🩹 Fixes
no-useless-template-expression -> no-unnecessary-template-expression
eslint-plugin: [no-unnecessary-type-assertion] combine template literal check with
constvariable checkeslint-plugin: [dot-notation] fix false positive when accessing private/protected property with optional chaining
eslint-plugin: [explicit-member-accessibility] refine report locations
eslint-plugin: [no-unnecessary-type-assertion] declares are always defined, so always check
declareseslint-plugin: [prefer-literal-enum-member] allow using member it self on allowBitwiseExpressions
eslint-plugin: [return-await] clean up in-try-catch detection and make autofixes safe
eslint-plugin: [member-ordering] also TSMethodSignature can be get/set
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.15.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.14.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.14.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.13.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.13.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.12.0Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
vitejs/vite-plugin-react (@vitejs/plugin-react)
v4.3.1Compare Source
Fix support for React Compiler with React 18
The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom
runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43When using a custom
runtimeModule, the plugin will not try to pre-optimizereact/compiler-runtimedependency.Reminder: Vite expect code outside of
node_modulesto be ESM, so you will need to update the gist withimport React from 'react'.evanw/esbuild (esbuild)
v0.22.0Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.21.0or~0.21.0. See npm's documentation about semver for more information.Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for
--platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use--packages=externalto work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.With this release, esbuild will now omit packages from the bundle by default when the platform is
node(i.e. the previous behavior of--packages=externalis now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do--packages=bundleto allow packages to be included in the bundle (i.e. the previous default behavior). Note that--packages=bundledoesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using--external:even when--packages=bundleis present.The
--packages=setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of/or.or..are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a#character) and TypeScript path remappings viapathsand/orbaseUrlintsconfig.json(which are applied first).Drop support for older platforms (#3802)
This release drops support for the following operating systems:
This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.
Note that this only affects the binary esbuild executables that are published to the
esbuildnpm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the
esbuild-wasmpackage and versions of node before node 17.4 (specifically thecrypto.getRandomValuesfunction).Update
await usingbehavior to match TypeScriptTypeScript 5.5 subtly changes the way
await usingbehaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.Allow
es2024as a target environmentThe ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression
/vflag. With--target=es2024, regular expressions that use the/vflag will now be passed through untransformed instead of being transformed into a call tonew RegExp.Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)
With this release, you should now be able to install the
esbuildnpm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.This was contributed by @ikmckenz.
Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)
The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a
.wasmfile without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.
This release publishes esbuild precompiled for WASI preview 1 to the
@esbuild/wasi-preview1package on npm (specifically the file@esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.Warn about
onResolveplugins not setting a path (#3790)Plugins that return values from
onResolvewithout resolving the path (i.e. without setting eitherpathorexternal: true) will now cause a warning. This is because esbuild only uses return values fromonResolveif it successfully resolves the path, and it's not good for invalid input to be silently ignored.Add a new Go API for running the CLI with plugins (#3539)
With esbuild's Go API, you can now call
cli.RunWithPlugins(args, plugins)to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.This was contributed by @edewit.
v0.21.5Compare Source
Fix
Symbol.metadataon classes without a class decorator (#3781)This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the
Symbol.metadataproperty to decorated classes if there was a decorator on the class element itself. However, the proposal says that theSymbol.metadataproperty should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.Allow unknown import attributes to be used with the
copyloader (#3792)Import attributes (the
withkeyword onimportstatements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load./bagel.jsas typebagel:Because of that, bundling this code with esbuild is an error unless the file
./bagel.jsis external to the bundle (such as with--bundle --external:./bagel.js).However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the
copyloader. That's because thecopyloader behaves similarly to--externalin that the file is left external to the bundle. The difference is that thecopyloader copies the file into the output folder and rewrites the import path while--externaldoesn't. That means the following will now work with thecopyloader (such as with--bundle --loader:.bagel=copy):Support import attributes with glob-style imports (#3797)
This release adds support for import attributes (the
withoption) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:
In addition, this change means plugins can now access the contents of
withfor glob-style imports.Support
${configDir}intsconfig.jsonfiles (#3782)This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence
${configDir}is now respected at the start ofbaseUrlandpathsvalues, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets basetsconfig.jsonfiles specified viaextendsrefer to the directory of the top-leveltsconfig.jsonfile. Here is an example:{ "compilerOptions": { "paths": { "js/*": ["${configDir}/dist/js/*"] } } }You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use
"${configDir}/dist/js/*"not`${configDir}/dist/js/*`). The syntax fortsconfig.jsonis still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes${configDir}in strings for certain path-like properties, and only at the beginning of the string.Fix internal error with
--supported:object-accessors=false(#3794)This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with
--supported:object-accessors=false. The reason is that esbuild introduced code that does{ get [name]() {} }which uses both theobject-extensionsfeature for the[name]and theobject-accessorsfeature for theget, but esbuild was incorrectly only checking forobject-extensionsand not forobject-accessors. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add--supported:object-extensions=false.jsx-eslint/eslint-plugin-jsx-a11y (eslint-plugin-jsx-a11y)
v6.9.0Compare Source
Fixed
img-redundant-alt: fixed multibyte character support#969#960Commits
6b5f096isNonInteractiveElement: Upgrade aria-query to 5.3.0 and axobject-query to 3.2.1"75d5dd7safe-regex-test4c7e78151a1ca7@babel/cli,@babel/core,@babel/eslint-parser,@babel/plugin-transform-flow-strip-types,@babel/register,eslint-doc-generator,object.entries1271ac1@babel/cli,@babel/core,@babel/register,aud,eslint-plugin-import,npmignore,object.assign540cb7a@babel/runtime,array-includes,es-iterator-helpers,hasown,object.fromentries,safe-regex-test5d14408aria-queryandaxobject-query, addls-enginestest to CI32fd82c@babel/core,@babel/eslint-parser,@babel/plugin-transform-flow-strip-types,eslint-doc-generatord1b4114summaryremains non-interactive6a048da@babel/runtime0a98ad8no-noninteractive-element-to-interactive-role: allowmenuitemradioandmenuitemcheckboxon <li>c0733f9@babel/runtime,safe-regex-test0d5321a961817faxe-coreb3559cfobject.entriesto dev deps1be7b70@babel/runtime2a48abb@babel/runtime1adec35jsx-eslint/eslint-plugin-react (eslint-plugin-react)
v7.34.3Compare Source
Fixed
prop-types]: null-check rootNode before calling getScope (#3762 @crnhrv)boolean-prop-naming]: avoid a crash with a spread prop (#3733 @ljharb)jsx-boolean-value]:assumeUndefinedIsFalsewithnevermust not allow explicittruevalue (#3757 @6uliver)no-object-type-as-default-prop]: enable rule for components with many parameters (#3768 @JulienR1)jsx-key]: incorrect behavior for checkKeyMustBeforeSpread with map callbacks (#3769 @akulsr0)prettier/prettier (prettier)
v3.3.2Compare Source
diff
Fix handlebars path expressions starts with
@(#16358 by @Princeyadav05)v3.3.1Compare Source
diff
Preserve empty lines in front matter (#16347 by @fisker)
Preserve explicit language in front matter (#16348 by @fisker)
Avoid line breaks in import attributes (#16349 by @fisker)
v3.3.0Compare Source
diff
🔗 Release Notes
vitejs/vite (vite)
v5.3.2Compare Source
location(#17528) (a8e2f6f), closes #17528v5.3.1Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 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 Mend Renovate using a curated preset maintained by