Split dependencies in the new structure about wasp HOT 1 OPEN

We've released Wasp 0.12.0 with some separation of dependencies, but we weren't thorough enough.

The issue still stands: figure out what belongs where and remove duplicates and redundancies.

Idea: Why not move all Wasp's dependencies from the user's package.json to the SDK's package.json. The main reasons against doing this were:

• This packages (e.g., typescript, react) are so crucial to Wasp that they should be listed in the package.json explicitly.
• What happens if the user (by accident) specifies one of these dependencies themselves? Does it break the app?

Finally, decide which packages can and should be peer dependencies (or dev dependencies).

Especially pay attention to:

• Types (e.g., @types/react, @types/react-router-dom) - Where should these go? Investigate the implications of putting them into each possible location:
  • user:dependencies vs user:devDependencies vs sdk:dependencies vs sdk:devDependencies.
• Packages Wasp implicitly needs - Packages that Wasp doesn't list as dependencies, but its code can't work without them (e.g., cors package for configuring middleware, possibley screen package for testing). This is bad API design on our part, and we should figure out what to do with those packages.
• Core packages - Wasp's core dependencies: React, Typescript, Vite, etc.

from wasp.