You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
since the launch of JSR 🎉 I've noticed, that you don't have to (or even should?) specify a version when importing a dependency.
You just import { dirname } from 'jsr:@std/path'; and it will resolve to the latest version by default.
When compared to deno.land it's recommended that you specify a version.
Otherwise you get squiggly lines on the import:
The resolution works completely fine either way:
Service
Specific version
No version
jsr
works ✔️
works ✔️
deno.land
works ✔️
works ✔️
I quite like not having to specify a version, as it checks for the newest dependencies on each run (if you don't use a lockfile).
But why is there a difference in how versions are expected?
Is the warning for "Implicitly using latest version..." necessary?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Deno community,
since the launch of JSR 🎉 I've noticed, that you don't have to (or even should?) specify a version when importing a dependency.
You just
import { dirname } from 'jsr:@std/path';
and it will resolve to the latest version by default.When compared to
deno.land
it's recommended that you specify a version.Otherwise you get squiggly lines on the import:
The resolution works completely fine either way:
I quite like not having to specify a version, as it checks for the newest dependencies on each run (if you don't use a lockfile).
But why is there a difference in how versions are expected?
Is the warning for "Implicitly using latest version..." necessary?
Kind regards
Beta Was this translation helpful? Give feedback.
All reactions