next-auth
Add default exports to package.json for better module support
#11224
Merged
Add default exports to package.json for better module support #11224
feat(core, frameworks-express): Add default exports to package.json f…
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| auth-docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 21, 2024 9:23am |
1 Ignored Deployment
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| next-auth-docs | ⬜️ Ignored (Inspect) | Visit Preview | Jun 21, 2024 9:23am |
@roonie007 is attempting to deploy a commit to the authjs Team on Vercel.
A member of the Team first needs to authorize it.
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@auth/core@0.33.0, npm/@libsql/client@0.6.0, npm/@oddbird/css-anchor-positioning@0.0.5, npm/@sveltejs/adapter-auto@1.0.0-next.91, npm/@types/eslint@8.56.10, npm/@types/react-dom@18.2.18, npm/@types/react@18.2.48, npm/@types/react@18.2.78, npm/algoliasearch@4.23.3, npm/classnames@2.5.1, npm/morgan@1.10.0, npm/next@14.2.3, npm/next@15.0.0-rc.0, npm/nextra-theme-docs@3.0.0-alpha.24, npm/nextra@3.0.0-alpha.24, npm/prisma@5.8.1, npm/pug@3.0.2, npm/react-dom@18.3.1, npm/react-dom@19.0.0-rc-4c2e457c7c-20240522, npm/react@18.3.1, npm/react@19.0.0-rc-4c2e457c7c-20240522, npm/shiki@1.3.0, npm/svelte-check@2.10.2, npm/svelte@4.2.9, npm/tsx@4.7.3, npm/typedoc-plugin-markdown@4.0.0-next.54
🚨 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 | CI |
|---|---|---|---|---|
| Install scripts | npm/svelte-preprocess@5.1.4 |
| 🚫 |
Next steps
What is an install script?
Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.
Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.
Take a deeper look at the dependency
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.
Remove the package
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.
Mark a package as acceptable risk
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/svelte-preprocess@5.1.4
Login to write a write a comment.
☕️ Reasoning
When using Auth + Express in a ModernJS project, I ran throught this error
Following this advice #9987 (comment) and adding a default option for each exported entry solves this problem, and everything ran as expected.
🧢 Checklist
🎫 Affected issues
Fixes ( I think ):
📌 Resources