Figure out Wasp's `tsconfig` story for the restructuring #1430

sodic · 2023-08-31T14:39:11Z

Decide on what to put in the user's TS config file, and how to reuse it in .wasp/out/server and .wasp/out/web-app.

The text was updated successfully, but these errors were encountered:

sodic · 2023-12-05T13:43:39Z

It seems like it's possible to reuse the entire tsconfig file in both modules of the generated code.

One thing to check: can we use local npm package installation (#1429 (comment)) for importing user dependencies?

sodic · 2024-02-29T14:42:54Z

We've published 0.12.0 without fully figuring out the TSconfig story.

I've opened up a new issue dedicated to this: #1827

sodic mentioned this issue Aug 31, 2023

Create a restructuring prototype #1426

Closed

infomiho added the restructuring label Sep 1, 2023

sodic changed the title ~~[Restructuring] Figure out Wasp's tsconfig story~~ Figure out Wasp's tsconfig story Sep 1, 2023

sodic mentioned this issue Dec 5, 2023

Implement the Restructuring #1427

Closed

sodic self-assigned this Dec 5, 2023

sodic changed the title ~~Figure out Wasp's tsconfig story~~ Figure out Wasp's tsconfig story for 0.12.0 Feb 29, 2024

sodic mentioned this issue Feb 29, 2024

Figure out Wasp's tsconfig story after Wasp 0.12.0 #1827

Open

sodic closed this as completed Feb 29, 2024

sodic changed the title ~~Figure out Wasp's tsconfig story for 0.12.0~~ Figure out Wasp's tsconfig story for the restructuring Feb 29, 2024

Provide feedback