moduleResolution as bundle

[antonioconselheiro]

NIPs that are not exported by default depend on the typescript configuration moduleResolution set as bundle.

I'm suggesting that it would be a good idea to include information about the need for this configuration in readme.md.

Maybe it's something obvious that I didn't understand, but it took me a while to understand out how to import these modules:

https://njump.me/note1d750tkpzs6lh5260x0z3r7w2n79ek82r9mg0kazmp6nms0ys8k9stvntte

[fiatjaf]

I am sorry, but the JavaScript ecosystem is ridiculous. The way dependencies and package managers and preprocessers and bundlers interact with each other changes all the time in a way that is not sane and this repository cannot help with that.

Maybe we should add a note saying that you are expected to have a PhD in Javascript Sciences before using the package?

[alexgleason]

Sorry, I may have broken it here: db53f37 Did not realize that would affect downstream packages. This is the correct setting for modern TypeScript, though.

[alexgleason]

It seems like we could change it to nodenext to make it work both ways.

[antonioconselheiro]

Just a suggestion, if you think it doesn't apply we can close the issue.

[alexgleason]

Nah you're probably not the only person going to experience this issue. I changed it to NodeNext in 6b43533 just now. Hopefully that will fix this issue.

[antonioconselheiro]

if these changes are confirmed I will no longer need my configuration moduleResolution set as bundle in my project?

[alexgleason]

You should still be using NodeNext or Bundler for modern projects. There's no reason to go back if you got it working. But I'm trying to fix it so it'll work both ways.

[alexgleason]

I think my commit will fix it. We need another version deployed to test it out.

@fiatjaf I ended up ripping out the GitHub actions for JSR because it's not working. I'll fix it later.