About Wasp repo and dependency versions
In Wasp repo, where are the dependency versions defined before generating a Wasp template?
3 Replies
Hi @isaiah. 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 don't have enough specific information to definitively answer where the dependency versions are defined in the Wasp repository before generating a Wasp template. The documents don't provide clear details about the internal structure of the Wasp repository or where exactly dependency versions are initially defined.
However, I can share some relevant information about how Wasp handles dependencies:
1. Wasp internally uses certain npm dependencies with specific versions. These are not directly visible to users but are part of Wasp's internal workings Docs > Project > Dependencies.
2. There was a plan to implement a
wasp deps list command that would list all of Wasp's internal dependencies along with their versions. This suggests that these dependencies are defined somewhere within the Wasp codebase, but the exact location is not specified Github Issue: Implement new command: wasp deps list.
3. The Wasp generator (specifically WebAppGenerator and ServerGenerator) seems to have knowledge of the npm dependencies, as mentioned in the discussion about implementing the wasp deps list command. However, the exact mechanism or location where these are defined is not provided in the given sources.
To get a definitive answer about where dependency versions are defined in the Wasp repository before template generation, you would need to examine the Wasp source code directly or consult with the Wasp development team.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @isaiah, 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?Your deps are defined in
package.json in the root of you project. Wasp's framework deps (internal deps that you can't control) will be located in .wasp/out/server and .wasp/out/web-app folders in package.json.
Can we help with something else?It's all good now.
I was only confused as to why an old toy Wasp project I have, had 2 different versions (root had v3.29.4 and .wasp had v4.24.3 ) of
rollup. So I wanted to check what's the actual version of rollup used by Wasp v0.15.2. I might have forgotten to reinstall node modules in that toy project as I updated Wasp version.