-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update npm (major) #34
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-npm
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+491
−1,270
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 19, 2024 21:27
57010ef
to
ac44906
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 20, 2024 01:58
ac44906
to
e8253ca
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 20, 2024 03:13
e8253ca
to
faca8b4
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 20, 2024 10:15
faca8b4
to
aec59ef
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 20, 2024 12:20
aec59ef
to
b35df82
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 21, 2024 10:58
b35df82
to
816b667
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 21, 2024 15:24
816b667
to
b3e59fc
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 21, 2024 18:50
b3e59fc
to
69d80bd
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 23, 2024 13:05
69d80bd
to
804ef0d
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 23, 2024 17:10
804ef0d
to
46fe535
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 23, 2024 22:02
46fe535
to
ee35641
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 24, 2024 10:14
ee35641
to
a80cf80
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
October 24, 2024 22:46
a80cf80
to
51b3027
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 22, 2025 17:05
ec3e5bc
to
08f23ea
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 23, 2025 01:05
08f23ea
to
766b30f
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 25, 2025 01:09
766b30f
to
0e45d4a
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 28, 2025 14:31
0e45d4a
to
00a4f4f
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 29, 2025 16:26
00a4f4f
to
d29c21e
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 30, 2025 12:44
d29c21e
to
2a9b7fa
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 30, 2025 18:02
2a9b7fa
to
08eab18
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 30, 2025 22:03
08eab18
to
11ce9ca
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
January 31, 2025 20:33
11ce9ca
to
3e3fb04
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
February 1, 2025 04:54
3e3fb04
to
e3d8dba
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
February 1, 2025 20:38
e3d8dba
to
dc5a832
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
February 3, 2025 17:55
dc5a832
to
681232c
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
February 3, 2025 21:44
681232c
to
fe05549
Compare
renovate
bot
force-pushed
the
renovate/major-npm
branch
from
February 4, 2025 09:23
fe05549
to
d885bdc
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:
^1.25.1
->^2.3.0
^1.25.1
->^2.3.0
^1.25.1
->^2.3.0
^3.1.2
->^5.0.3
^1.9.2
->^3.2.2
^9.1.0
->^10.0.1
9.15.2
->10.2.0
^1.25.1
->^2.3.0
^4.2.19
->^5.19.7
^3.0.5
->^4.0.2
^3.1.4
->^4.1.0
^2.6.0
->^3.0.1
^3.4.17
->^4.0.3
^5.4.11
->^6.0.11
Release Notes
shikijs/shiki (@shikijs/langs)
v2.3.0
Compare Source
🚀 Features
View changes on GitHub
v2.2.0
Compare Source
🚨 Breaking Changes
🚀 Features
markdown-it-async
integration - by @antfu in https://github.com/shikijs/shiki/issues/902 (4d59c)fallbackLanguage
on lazy mode - by @fuma-nama in https://github.com/shikijs/shiki/issues/912 (6a852)🐞 Bug Fixes
engine
required increateHighlighterCore
- by @antfu (1212f)htmlStyle
- by @antfu (eab5b)engine
options - by @antfu (10a6f)createCommentNotationTransformer
, fix #907 - by @antfu in https://github.com/shikijs/shiki/issues/907 (8386b)View changes on GitHub
v2.1.0
Compare Source
🚀 Features
markdown-it-async
integration - by @antfu in https://github.com/shikijs/shiki/issues/902 (4d59c)View changes on GitHub
v2.0.3
Compare Source
🐞 Bug Fixes
engine
options - by @antfu (10a6f)View changes on GitHub
v2.0.2
Compare Source
🐞 Bug Fixes
engine
required increateHighlighterCore
- by @antfu (1212f)View changes on GitHub
v2.0.1
Compare Source
🚀 Features
🐞 Bug Fixes
htmlStyle
- by @antfu (eab5b)View changes on GitHub
v2.0.0
Compare Source
Read the announcement: Shiki v2
View changes on GitHub
v1.29.2
Compare Source
🚨 Breaking Changes
🚀 Features
markdown-it-async
integration - by @antfu in https://github.com/shikijs/shiki/issues/902 (4d59c)🐞 Bug Fixes
engine
required increateHighlighterCore
- by @antfu (1212f)htmlStyle
- by @antfu (eab5b)engine
options - by @antfu (10a6f)View changes on GitHub
v1.29.1
Compare Source
🚀 Features
shiki/types
- by @antfu (0b027)View changes on GitHub
v1.29.0
Compare Source
🚀 Features
matchAlgorithm
option for new matching algorithm - by @fuma-nama and @antfu in https://github.com/shikijs/shiki/issues/835 (ceca9)View changes on GitHub
v1.28.0
Compare Source
🚀 Features
🐞 Bug Fixes
lazy
performance - by @fuma-nama in https://github.com/shikijs/shiki/issues/896 (5c10f)View changes on GitHub
v1.27.2
Compare Source
No significant changes
View changes on GitHub
v1.27.1
Compare Source
🚀 Features
EmulatedRegExp
as pure - by @antfu (11ef0)View changes on GitHub
v1.27.0
Compare Source
🚀 Features
View changes on GitHub
v1.26.2
Compare Source
🚀 Features
View changes on GitHub
v1.26.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.26.0
Compare Source
🚀 Features
View changes on GitHub
sveltejs/vite-plugin-svelte (@sveltejs/vite-plugin-svelte)
v5.0.3
Compare Source
Patch Changes
v5.0.2
Compare Source
Patch Changes
code
property to changes in svelte5 (#1044)v5.0.1
Compare Source
Patch Changes
v5.0.0
Compare Source
Major Changes
Handle Vite 6 breaking change and remove Vite 5 handling (#1020)
Support Vite 6 (#1026)
Minor Changes
Add
esm-env
tossr.noExternal
by default to resolve its conditions with Vite (#1020)Support
?inline
query on Svelte style virtual modules (#1024)Patch Changes
remove vite6 beta from peer range (#1035)
Allow script tags to span multiple lines (
0db95a9
)Updated dependencies [
4fefbc2
,e262266
]:v4.0.4
Compare Source
Patch Changes
1a91581
)v4.0.3
Compare Source
Patch Changes
code
property to changes in svelte5 (#1046)v4.0.2
Compare Source
Patch Changes
5309d7b
)v4.0.1
Compare Source
Patch Changes
v4.0.0
Compare Source
Major Changes
only prebundle files with default filenames (.svelte for components, .svelte.(js|ts) for modules) (#901)
remove support for Svelte 4 (#892)
breaking(types): some types that have been unintentionally public are now private (#934)
disable script preprocessing in vitePreprocess() by default because Svelte 5 supports lang=ts out of the box (#892)
replaced svelte-hmr with Svelte 5 compiler hmr integration (#892)
Minor Changes
allow infix notation for svelte modules (#901)
Previously, only suffix notation
.svelte.js
was allowed, now you can also use.svelte.test.js
or.svelte.stories.js
.This helps when writing testcases or other auxillary code where you may want to use runes too.
feat(config): dynamically extract list of svelte exports from peer dependency so that new exports work automatically" (#941)
feat(warnings): change default loglevel of warnings originating from files in node_modules to debug. To see them call
DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build
. (#989)Patch Changes
fix: make defaultHandler a required argument for onwarn in plugin options (#895)
prebundle with dev: true by default (#901)
fix(dev): compile with hmr: false for prebundled deps as hmr does not work with that (#950)
fix: ensure svelte modules correctly run in DEV mode (#906)
ensure consistent use of compileOptions.hmr also for prebundling (#956)
fix(optimizeDeps): avoid to optimise server only entrypoints of svelte that are never used on the client (#941)
update peer on workspace packages to avoid packages bumping each other (#916)
export PluginOptions interface (#976)
Remove log about experimental status of Svelte 5. Note that breaking changes can still occur while vite-plugin-svelte 4 is in prerelease mode (#894)
fix: ensure vite config is only resolved once during lazy init of vitePreprocess (#912)
fix(vitePreprocess): default to build config so that svelte-check does not trigger dev-only plugins (#931)
fix: only apply infix filter to basename (#920)
fix: disable hmr when vite config server.hmr is false (#913)
fix(dev): make sure custom cssHash is applied consistently even for prebundled components to avoid hash mismatches during hydration (#950)
Updated dependencies [
22baa25
,49324db
,e9f048c
,213fedd
]:pilcrowonpaper/arctic (arctic)
v3.2.2
Compare Source
Origin
header to requests (#260).v3.2.1
Compare Source
refreshAccessToken()
method to Figma provider (#258).v3.2.0
Compare Source
v3.1.3
Compare Source
scope
parameter.v3.1.2
Compare Source
TikTok
provider (#249).v3.1.1
Compare Source
v3.1.0
Compare Source
v3.0.0
Compare Source
Arctic v3 is here! This is a small major release that adds support for public OAuth clients. There are only a few breaking changes and most breaking changes are small.
Changes
clientSecret
parameter fromEtsy
constructor.codeVerifier
parameter tocreateAuthorizationURL()
andvalidateAuthorizationCode()
inAuth0
,Discord
,Spotify
,WorkOS
.domain
parameter withbaseURL
parameter forAuthentik
,GitLab
constructor.poolURL
parameter withdomain
parameter forAmazonCognito
constructor.scopes
parameter torefreshAccessToken()
inAmazonCognito
,MicrosoftEntraId
.MyAnimeList
constructor.OAuth2Client
.UnexpectedResponseError
andUnexpectedErrorResponseBodyError
errors.null
asclientSecret
inAmazonCognito
,Auth0
,Authentik
,Bungie
,Discord
,GitLab
,KeyCloak
,MicrosoftEntraId
,Roblox
,Salesforce
,Spotify
,Twitter
,WorkOS
constructor.scopes
parameter inStrava.createAuthorizationURL()
.v2.3.4
refreshAccessToken()
method to Figma provider (#256).v2.0.0
Major changes
createAuthorizationURL()
no longer returns aPromise
validateAuthorizationCode()
andrefreshAccessToken()
returnsOAuth2Tokens
validateAuthorizationCode()
andrefreshAccessToken()
can throw one ofOAuth2RequestError
,ArcticFetchError
, orError
openid
and those required by the providerApple
,GitHub
,GitLab
,MicrosoftEntraId
,MyAnimeList
,Okta
,Osu
, andSalesforce
options.scope
parameter fromcreateAuthorizationURL()
OAuth2Provider
andOAuth2ProviderWithPKCE
createAuthorizationURL()
provider methodsMinor changes
refreshAccessToken()
toGitHub
createAuthorizationURL()
returnsAuthorizationCodeAuthorizationURL
decodeIdToken()
Patch changes
@oslojs/oauth2
dependencyprettier/eslint-config-prettier (eslint-config-prettier)
v10.0.1
Compare Source
eslint-config-prettier
10.0.1
What's Changed
@stylistic/eslint-plugin
by @abrahamguo in https://github.com/prettier/eslint-config-prettier/pull/272New Contributors
Full Changelog: prettier/eslint-config-prettier@v9.1.0...v10.0.1
v10.0.0
Compare Source
Major Changes
5be64be
Thanks @abrahamguo! - add support for @stylistic formatting rulespnpm/pnpm (pnpm)
v10.2.0
Compare Source
Minor Changes
Packages executed via
pnpm dlx
andpnpm create
are allowed to be built (run postinstall scripts) by default.If the packages executed by
dlx
orcreate
have dependencies that have to be built, they should be listed via the--allow-build
flag. For instance, if you want to run a package calledbundle
that hasesbuild
in dependencies and want to allowesbuild
to run postinstall scripts, run:Related PR: #9026.
Patch Changes
pnpm deploy
fails to read the correctprojectId
when the deploy source is the same as the workspace directory #9001.overrides
from adding invalid version ranges topeerDependencies
by keeping thepeerDependencies
and overriding them with proddependencies
#8978.pnpm approve-builds
.v10.1.0
Compare Source
Minor Changes
pnpm ignored-builds
#8963.pnpm approve-builds
#8963.optimistic-repeat-install
. When enabled, a fast check will be performed before proceeding to installation. This way a repeat install or an install on a project with everything up-to-date becomes a lot faster. But some edge cases might arise, so we keep it disabled by default for now #8977.Patch Changes
pnpm install
, thepreprepare
andpostprepare
scripts of the project should be executed #8989.workspace:
andcatalog:
to be part of wider version range inpeerDependencies
.pnpm deploy
should inherit thepnpm
object from the rootpackage.json
#8991.node_modules
in a sub-project of a monorepo is detected as out-of-date #8959.pnpm
to execute other scripts duringpnpm install
withverify-deps-before-run=install
#8954.strip-ansi
with the built-inutil.stripVTControlCharacters
#9009.v10.0.0
Compare Source
Major Changes
Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to allow lifecycle scripts of specific dependencies, they should be listed in the
pnpm.onlyBuiltDependencies
field ofpackage.json
#8897. For example:pnpm link
behavior updated:The
pnpm link
command now adds overrides to the rootpackage.json
.pnpm link
from the package’s directory. Previously, you needed to usepnpm link -g
.Related PR: #8653
Secure hashing with SHA256:
Various hashing algorithms have been updated to SHA256 for enhanced security and consistency:
node_modules/.pnpm
are now hashed with SHA256.packageExtensionsChecksum
field ofpnpm-lock.yaml
is now SHA256.Configuration updates:
manage-package-manager-versions
: enabled by default. pnpm now manages its own version based on thepackageManager
field inpackage.json
by default.public-hoist-pattern
: nothing is hoisted by default. Packages containingeslint
orprettier
in their name are no longer hoisted to the root ofnode_modules
. Related Issue: #8378Upgraded
@yarnpkg/extensions
to v2.0.3. This may alter your lockfile.virtual-store-dir-max-length
: the default value on Windows has been reduced to 60 characters.Reduced environment variables for scripts:
During script execution, fewer
npm_package_*
environment variables are set. Onlyname
,version
,bin
,engines
, andconfig
remain.Related Issue: #8552
All dependencies are now installed even if
NODE_ENV=production
. Related Issue: #8827Changes to the global store:
Store version bumped to v10.
Some registries allow identical content to be published under different package names or versions. To accommodate this, index files in the store are now stored using both the content hash and package identifier.
This approach ensures that we can:
Related PR: #8510
Related Issue: #8204
More efficient side effects indexing. The structure of index files in the store has changed. Side effects are now tracked more efficiently by listing only file differences rather than all files.
Related PR: #8636
A new
index
directory stores package content mappings. Previously, these files were infiles
.Other breaking changes:
#
character is now escaped in directory names withinnode_modules/.pnpm
.Related PR: #8557
pnpm add --global pnpm
orpnpm add --global @​pnpm/exe
now fails with an error message, directing you to usepnpm self-update
instead.Related PR: #8728
Related Issue: #8833
pnpm deploy
command now only works in workspaces that haveinject-workspace-packages=true
. This limitation is introduced to allow us to create a proper lockfile for the deployed project using the workspace lockfile.pnpm test
now passes all parameters after thetest
keyword directly to the underlying script. This matches the behavior ofpnpm run test
. Previously you needed to use the--
prefix.Related PR: #8619
node-gyp
updated to version 11.pnpm deploy
now tries creating a dedicated lockfile from a shared lockfile for deployment. It will fallback to deployment without a lockfile if there is no shared lockfile orforce-legacy-deploy
is set totrue
.Minor Changes
Added support for a new type of dependencies called "configurational dependencies". These dependencies are installed before all the other types of dependencies (before "dependencies", "devDependencies", "optionalDependencies").
Configurational dependencies cannot have dependencies of their own or lifecycle scripts. They should be added using exact version and the integrity checksum. Example:
Related RFC: #8.
Related PR: #8915.
New settings:
New
verify-deps-before-run
setting. This setting controls howpnpm
checksnode_modules
before running scripts:install
: Automatically runpnpm install
ifnode_modules
is outdated.warn
: Print a warning ifnode_modules
is outdated.prompt
: Prompt the user to confirm runningpnpm install
ifnode_modules
is outdated.error
: Throw an error ifnode_modules
is outdated.false
: Disable dependency checks.Related Issue: #8585
New
inject-workspace-packages
setting enables hard-linking all local workspace dependencies instead of symlinking them. Previously, this could be achieved usingdependenciesMeta[].injected
, which remains supported.Related PR: #8836
Faster repeat installs:
On repeated installs,
pnpm
performs a quick check to ensurenode_modules
is up to date.Related PR: #8838
pnpm add
integrates with default workspace catalog:When adding a dependency,
pnpm add
checks the default workspace catalog. If the dependency and version requirement match the catalog,pnpm add
uses thecatalog:
protocol. Without a specified version, it matches the catalog’s version. If it doesn’t match, it falls back to standard behavior.Related Issue: #8640
pnpm dlx
now resolves packages to their exact versions and uses these exact versions for cache keys. This ensurespnpm dlx
always installs the latest requested packages.Related PR: #8811
No
node_modules
validation on certain commands. Commands that should not modifynode_modules
(e.g.,pnpm install --lockfile-only
) no longer validate or purgenode_modules
.Related PR: #8657
v9.15.5
: pnpm 9.15.5Compare Source
Patch Changes
pnpm install
, thepreprepare
andpostprepare
scripts of the project should be executed #8989.strip-ansi
with the built-inutil.stripVTControlCharacters
#9009.Platinum Sponsors
Gold Sponsors
This PR was generated by Mend Renovate. View the repository job log.