Content
@
https://warpcast.com/~/channel/sys
0 reply
0 recast
0 reaction
Phil Cockfield
@pjc
2 replies
0 recast
5 reactions
Rafi
@rafi
Dear Phil, Your designs deserve better image quality. Thank you, Yours fans
1 reply
0 recast
1 reaction
Phil Cockfield
@pjc
You're the best Rafi (in SF!). This is the ESM import-map aliasing I'm laying down between Deno (modules within a "workspace") and Vite as a bundler.
1 reply
0 recast
1 reaction
Rafi
@rafi
Did you get workspaces to work in Vite? It didn’t work for me when I used the official vite plugin 1mo ago
1 reply
0 recast
1 reaction
Phil Cockfield
@pjc
Ah, yeah - no I'd written my own solution before they released that plugin, then when I tried it (assuming they'd have a better approach than me) it didn't work for me either. What I was doing was clean and easily reasonable about, so I've stayed with it - and now I'm really glad, because this whole thing (and future things to come) are really just simple mappings between ESM import names, and known locations in the workspace. In the system, I've ended up writing this and breaking it out from super generic (the ESM "module specifier" standard, with parsers and validators etc) through to a "Deno" specific driver module, that is scoped to deal specifically with the way Deno chooses to structure it's workspace references. Ref: ESM ("Standard") https://jsr.io/@sys/std → ESM ↓ https://jsr.io/@sys/std/0.0.123/src/m.Esm Deno ("Driver") https://jsr.io/@sys/driver-deno https://jsr.io/@sys/driver-deno/0.0.79/src/ns.Runtime/m.DenoFile/u.workspace.ts
1 reply
0 recast
0 reaction
