mirror of
https://github.com/wasp-lang/wasp.git
synced 2024-12-27 02:52:22 +03:00
994a58f0dc
* Improved Wasp AI CLI experience. * fix * Added CLI Usage, polished CLI commands. * Added choice of temperature. * Added styling. * Added more sophisticated, terminal-only styling. * fix * Updated Mage to use new Wasp CLI + added some messaging to CLI. * fix * Created wasp-ai/README, updated waspc/README. * Moved wasp-ai/ to mage/. * Final polishing (docs, readmes, messaging). * fix * Added tests for LogMsg. * Updated versions of test apps to 0.12. * fix * fix * Update mage/README.md * fix * fix |
||
|---|---|---|
| .. | ||
| deploy | ||
| prisma | ||
| studio | ||
| ts-inspect | ||
| 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.