5 ms·
Why use '$' as the package namespace prefix/identifier instead of the already agreed upon convention of '@'? E.g. '@fresh/{package}' vs '$fresh/{package}'. See
by halfmatthalfcat 4y ago
Why use '$' as the package namespace prefix/identifier instead of the already agreed upon convention of '@'? E.g. '@fresh/{package}' vs '$fresh/{package}'.
Seems like a departure from the norm for no reason unless there's some Deno particularity about it.
- 0x6c6f6c 4y agoBecause the '@' convention is for organizations, not the actual package, e.g. '@company/pkg'. In this case, '$fresh' is the actual package, and there is no organization name. This just may be the Deno standard for their import mapping functionality since they also do full URLs for imports like Go (sans schema) normally. Deno is also just not exactly like JS ecosystems, and that's exactly the point too. Opinionated defaults, out-of-the-box support for TypeScript, death to NPM.
- tbeseda 4y agoI think the convention of `~somepackage` is more common than using `@` as a shortcut.