mirror of https://github.com/wasp-lang/wasp.git synced 2024-09-11 15:26:19 +03:00

History

Martin Šošić 994a58f0dc Wasp ai cli mage (#1601 ) * 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		2023-12-22 15:14:38 +01:00
..
deploy	Sets the minimum number of Fly machines to 1 (#1535 )	2023-11-06 15:47:45 +01:00
prisma	Wasp ai cli mage (#1601 )	2023-12-22 15:14:38 +01:00
studio	Wasp Studio [experimental] (#1483 )	2023-10-10 12:17:05 +02:00
ts-inspect	[waspls] cleanup extimport code (#1292 )	2023-07-07 08:21:33 -04: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.