vercel[bot]
commented
5 months ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| sharrr-svelte | ❌ Failed (Inspect) | Jan 19, 2024 2:02pm |
Closed dependabot[bot] closed 5 months ago
vercel[bot]
commented
5 months ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| sharrr-svelte | ❌ Failed (Inspect) | Jan 19, 2024 2:02pm |
socket-security[bot]
commented
5 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/@sveltejs/kit@2.4.0 | Transitive: environment, filesystem, network, shell | +54 |
211 MB |
🚮 Removed packages: npm/@sveltejs/kit@1.25.1
socket-security[bot]
commented
5 months ago 🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
| Alert | Package | Note | Source |
|---|---|---|---|
| Invalid package.json | npm/sirv@2.0.4 |
|
Package has an invalid package.json and can cause installation problems if you try to use it.
Fix syntax errors in the invalid package.json and publish a new version with a valid package.json. Consumers can use npm overrides to force a version that does not have this problem if one exists.
Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.
If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.
To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/sirv@2.0.4
dependabot[bot]
commented
5 months ago Superseded by #189.
Bumps @sveltejs/kit from 1.25.1 to 2.4.0.
Release notes
Sourced from
@sveltejs/kit's releases.... (truncated)
Changelog
Sourced from
@sveltejs/kit's changelog.... (truncated)
Commits
64f414bVersion Packages (#11670)288f731feat: implementread(#11649)6200a48Version Packages (#11662)119971cfix: log a warning if fallback page overwrites prerendered page (#11661)0bd1a4eVersion Packages (#11660)5a1fc41fix: don't stash away originalhistorymethods so other libs can monkeypatc...fe7cee5chore: upgrade dependencies (#11632)99612acVersion Packages (#11614)972a985Revert "feat: include server assets for Vercel serverless functions" (#11644)fe1a11efeat: include server assets for Vercel serverless functions (#10979)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show