Wasp TS SDK package
Quick question why wasp-config package https://github.com/wasp-lang/wasp/tree/v0.16.0/waspc/packages/wasp-config is not published on npm direcly? but installed as link to wasp installed in system
GitHub
wasp/waspc/packages/wasp-config at v0.16.0 · wasp-lang/wasp
The fastest way to develop full-stack web apps with React & Node.js. - wasp-lang/wasp
1 Reply
Hi @Fecony. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, I can offer some insight into why the Wasp SDK package is not published directly on npm.
The Wasp team has been working on restructuring how they handle dependencies and SDK packages. According to Github Issue #1429, they decided to use local package installation for the SDK:
"We'll be installing our sdk package using a local package installation from somewhere inside the
.wasp directory and using NPM's local dependency option for installing it."
This approach allows Wasp to use the SDK as a proper NPM package during runtime, while still maintaining flexibility and control over its distribution. The SDK is installed locally within the Wasp project structure, rather than being published as a separate package on npm.
This decision was made to simplify the development process and ensure that the SDK version always matches the installed Wasp version. It allows Wasp to generate and update the SDK based on the current state of the code without needing to publish new versions to npm for every change.
However, it's worth noting that the Wasp team is still evolving their approach to package management and SDK distribution. The current method may change in future versions as they continue to refine their development process and respond to user needs.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Fecony, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?