wasp-lang/wasp
1
1
Fork 0
mirror of https://github.com/wasp-lang/wasp.git synced 2024-12-25 18:13:52 +03:00
Code Issues Projects Releases Wiki Activity
90baa9423e
wasp/waspc/packages
History
Filip Sodić 01af22f6e3
Make server and client fields optional (#2351)
2024-10-21 22:37:05 +02:00
..
deploy Override serverUrl in wasp deploy fly deploy command (#2234) 2024-09-02 15:56:33 +02:00
prisma Update Prisma to v5 (#2231) 2024-09-04 15:16:25 +02:00
studio Bump braces from 3.0.2 to 3.0.3 in /waspc/packages/studio (#2147) 2024-07-03 13:45:07 +02:00
ts-inspect Bump braces from 3.0.2 to 3.0.3 in /waspc/packages/ts-inspect (#2123) 2024-06-25 17:48:21 +02:00
wasp-config Make server and client fields optional (#2351) 2024-10-21 22:37:05 +02:00
README.md [waspls] cleanup extimport code (#1292) 2023-07-07 08:21:33 -04:00

README.md

Testing Packages Locally

Run tools/install_packages_to_data_dir.sh to compile the packages and copy them into data/. Then you can use cabal run as normal, or you can cabal install and then use wasp-cli.

Adding a New Package

Create a directory in this folder to contain the new package. It should have a build script inside package.json as well as a start script that calls the compiled code.

Then, in data-files inside waspc.cabal, add these files:

packages/<package-name>/package.json
packages/<package-name>/package-lock.json
packages/<package-name>/dist/**/*.js

The last line assumes the project is compiled to .js files inside the dist directory. You should adjust this and/or add more file extensions if needed.

CI Builds/Release

The CI workflow runs the package install script, and tools/make_binary_package.sh takes care of copying data files into the release archive.