-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
refactor(kit,nuxt,vite,webpack)!: remove legacy require utils in favour ofjiti
#28008
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
Conversation
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/vue-bundle-renderer@2.1.0 |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat 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 dependencyTake 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 packageIf 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 riskTo ignore an alert, reply with a comment starting with
|
pluginFn = requireModule(pluginName, { paths: [cwd] }) | ||
} | ||
const path = jiti.esmResolve(pluginName) | ||
const pluginFn = (await jiti.import(path)) as (opts: Record<string, any>) => Plugin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jiti will do esmResolve i think in module.ts only reason was that we need to also reuse same path
in resolved meta
🔗 Linked issue
📚 Description
This follows up on #27995 to remove legacy CJS utils and rely on jiti to resolve/import modules and postcss plugins.
We use
resolvePath
frommlly
in other places which we might leave in place as it has lower overhead.👉 Modules should now support Nuxt aliases! 🙌
🚨 Breaking changes
Internal CJS utils (marked as deprecated) have now been removed. They were never meant for external use anyway. We could add an example to the upgrade guide.