Closed Bubblyworld closed 1 year ago
The workflow currently being recommended here is jspm i denoland:fresh/runtime.ts -m deno.json
or jspm i denoland:fresh/runtime.ts -o browser.html --env=browser
for dual browser / Deno workflows.
Ah I realise you meant this for secondaries. This is not something we want to do actually because the deno.json
is an exact resolution map not a constraint, whereas package management always operates on constraints (ie package.json dependencies).
fresh
uses an import map for bare specifiers likepreact
, but the generator currently ignores thedeno.json
, so when it tries to resolvepreact
we hit the global fallback, which is to usenpm:preact
, and the deno provider throws as it doesn't support the npm registry.