bun run build from the translucent-blueprint folder should produce a valid artifact for any platform that supports the node apis now.
I found one limitation WRT imports described here. Essentially, typescript won't transpile import foo from './foo to import foo from './foo.js no matter what you do. Likewise, the node team specifically refuses to allow./foo style ESM imports. Luckily, Bun can interpret xxx.js as xxx.ts when handling imports, so the simplest solution here is just to use from xxx.js style imports in translucent-blueprint. It sure looks silly, though.
Also fixed up the test I added to be a lil more Bun-idiomatic, since I had to touch it anyway.
Closes #38
bun run buildfrom thetranslucent-blueprintfolder should produce a valid artifact for any platform that supports the node apis now.I found one limitation WRT imports described here. Essentially, typescript won't transpile
import foo from './footoimport foo from './foo.jsno matter what you do. Likewise, the node team specifically refuses to allow./foostyle ESM imports. Luckily, Bun can interpretxxx.jsasxxx.tswhen handling imports, so the simplest solution here is just to usefrom xxx.jsstyle imports intranslucent-blueprint. It sure looks silly, though.Also fixed up the test I added to be a lil more Bun-idiomatic, since I had to touch it anyway.