60233dcbcc
Co-authored-by: Mihovil Ilakovac <mihovil@ilakovac.com> Co-authored-by: Martin Šošić <Martinsos@users.noreply.github.com> Co-authored-by: Filip Sodić <filip.sodic@gmail.com> Co-authored-by: Filip Sodić <filip.sodic@fer.hr>
1.2 KiB
| title |
|---|
| Dependencies |
Specifying npm dependencies in Wasp project is done via the dependencies field in the app declaration, in the following way:
app MyApp {
title: "My app",
// ...
dependencies: [
("redux", "^4.0.5"),
("react-redux", "^7.1.3")
]
}
You will need to re-run wasp start after adding a dependency for Wasp to pick it up.
The quickest way to find out the latest version of a package is to run:
npm view <package-name> version
:::note Using Packages that are Already Used by Wasp Internally In the current implementation of Wasp, if Wasp is already internally using a certain npm dependency with a certain version specified, you are not allowed to define that same npm dependency yourself while specifying a different version. If you do that, you will get an error message telling you which exact version you have to use for that dependency. This means Wasp dictates exact versions of certain packages, so for example you can't choose version of React you want to use.
We are currently working on a restructuring that will solve this and some other quirks that the current dependency system has: check issue #734 to follow our progress. :::