Fix autocomplete for wasp package

[sodic]

Patrially fixes #1839.

This PR enables the IDE to properly autocomplete imports exposed from node_modules/wasp.

Here's how it looks:

autocomplete.mp4

After we merge this, all that's left is hiding the stuff we don't want the user to see: #1922.

[sodic]

I got here by trial and error, but bundler seems the most (if not only) appropriate option for our setup.

By implicit defaults cascading, this got set CommonJs, which is why it failed to recognize ES exports from the wasp package.

The cascading was:

• target was unset and defaulted to ES3.
• module was unset and defaulted to CommonJS because the target was ES3.
• moduleResolution was unset and defaulted to Node because module was CommonJS.
• moduleResolution: Node can't work with ES imports.

Source for all rules: https://www.typescriptlang.org/tsconfig#module

[infomiho]

Given that this is in the user's tsconfig.json, does this mean that only the new newly created projects will get the benefits of these changes?

Do we also need to update all other templates? Specifically the ones you get when running wasp new:

[1] basic (default)
    Simple starter template with a single page.
[2] todo-ts
    Simple but well-rounded Wasp app implemented with Typescript & full-stack type safety.
[3] saas
    Everything a SaaS needs! Comes with Auth, ChatGPT API, Tailwind, Stripe payments and more. Check out https://opensaas.sh/ for more details.
[4] embeddings
    Comes with code for generating vector embeddings and performing vector similarity search.
[5] ai-generated
    🤖 Describe an app in a couple of sentences and have Wasp AI generate initial code for you. (experimental)

[sodic]

Given that this is in the user's tsconfig.json, does this mean that only the new newly created projects will get the benefits of these changes?

Yes, any ideas on what we can do here?

Do we also need to update all other templates? Specifically the ones you get when running wasp new:

Apparently yes, nice catch! I thought they all used skeleton... We really do need to change those names 😄

[Martinsos]

Yeah, those names are a bit tricky. But don't they use skeleton? Except for open-saas?

[sodic]

I tested it out, and unfortunately not (only basic and ai-generated do):

$ for i in {basic,todo-ts,saas,embeddings,ai-generated}; do cabal run wasp-cli new filip-test-$i -- -t $i; done
...
$ rg moduleResolution filip-test* -l
filip-test-basic/tsconfig.json
filip-test-ai-generated/tsconfig.json
$

[sodic]

What do I do with that?

Should I do anything now or do we take care of it in the release process: https://github.com/wasp-lang/wasp/tree/main/waspc#typical-release-process.

[Martinsos]

I think it makes sense to do now, when we still have context about it and it is fresh.

But you can do it another PR if you wish! Or maybe you even have to, for these starters.

[sodic]

Here they are:

• Update tsconfig.json to autocomplete imports starters#5
• Update tsconfig.json to autocomplete imports open-saas#92

[Martinsos]

Awesome!