Resolving ext-src imports in the SDK if the user declares an import with the .js ext

[infomiho]

Users get a weird error saying they can't import queries.js.js something something.

I've reproduced with the latest Wasp version: 0.13.2

As far as I can see, it seems related to the exports fields and the ext-src/* entry 😄

Two instances on Discord:

• https://ptb.discord.com/channels/686873244791210014/1250145383322091561/1250145383322091561
• https://ptb.discord.com/channels/686873244791210014/1249857194925752401/1249857194925752401

[Martinsos]

Sending this back to triage, multiple people had this and error message is quite confusing, we should take care of it.

[Martinsos]

This is in a way related to #2087 , as they might share a solution, which is us completely forbidding, in main.wasp, to have .js or .ts extensions in ext imports, or, another solution, somehow additionally processing extensions to fit with what Wasp requires.

[Martinsos]

User said following:

Was odd because the issue was nonexistent until one day it wasn't.

That is peculiar! Might it mean that one of the deps updated minor version and caused this that way?