feat(lint): no-unversioned-import rule #30609
Merged
Conversation
This file contains hidden or 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
bartlomieju
approved these changes
Sep 3, 2025
|
This doesn't just apply to non-versioned specifiers. It applies to all bare specifiers, even if they specify a version. If this is the case we need something like devDependencies to distinguish between dependencies needed for the program and ones needed for tests, benches, etc. |
Can you open an issue? This is a closed PR |
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.
Bans using npm/jsr imports without specifying a version requirement.
It's bad to not specify a version requirement because without a lockfile Deno will always pull in the latest version of a package, which could cause your code to stop working if the package ever publishes a breaking change.