-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
feat(core): add specifier type for * & latest #174
Labels
Comments
Sorry @JamieMason, I searched the repo for similar issues but totally missed that one. I agree with the solution you proposed! |
No problem at all 👍 |
JamieMason
changed the title
Feature request: ban the
feat(core): add specifier type for * & latest
Dec 29, 2023
*
protocol
JamieMason
added a commit
that referenced
this issue
Dec 29, 2023
Released in 12.2.0. 👋 If anyone reading this finds syncpack useful, please tell people about it. |
Thanks @JamieMason, it worked great with "versionGroups": [
{
"label": "Ban * protocol in devDependencies",
"dependencyTypes": ["dev"],
"specifierTypes": ["latest"],
"isBanned": true
}
] I made a PR to fix the examples in the documentation: #185. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Hello, thank you for this great tool! I have a question about the usage of the
*
protocol. While it's nice forpeerDependencies
, I find it less ideal indevDependencies
where I prefer to have an exact version.Suggested Solution
I propose the following configuration to support banning a specific version of a package, serving as a potential security measure:
This would allow us to explicitly disallow the use of the
*
protocol in devDependencies.Help Needed
I am willing to create a PR if the suggested solution aligns with the project's goals.
The text was updated successfully, but these errors were encountered: