feat: Includes motoko-dev-server in new motoko projects
Description
The Motoko project now includes a few new quality-of-life enhancements:
npm startnow starts themotoko-dev-serverin addition to thewebpackserver.- This means that you can now use the
motoko-dev-serverto hot-reload your motoko canisters and frontends as you make changes.
- This means that you can now use the
mopspackage manager is now included and configured- This installs the
motoko-baseandtestlibraries
- This installs the
- hello world now includes a
lib.moandlib.test.mofile- This demonstrates write tests for your canisters and run them with
npm run test:motoko
- This demonstrates write tests for your canisters and run them with
Fixes #SDK-991
How Has This Been Tested?
Manually compiling the rust and motoko new projects
- dfx deploy
- visiting the webpage
- npm start
- visiting the webpage
Checklist:
- [x] The title of this PR complies with Conventional Commits.
- [x] I have edited the CHANGELOG accordingly.
- [x] I have made corresponding changes to the documentation.
Noting here - mops sources failed during CI with exit status: 254. It may be that mops isn't mature enough yet
Which version of Node.js is being used in the CI?
(Update: it's Node 18.x)
@krpeacock @ZenVoich @dfx-json, these CI errors are apparently caused by the replica timing out rather than an issue with Mops (relevant log output).
I temporarily switched the default mops.toml dependencies to use GitHub repositories to unblock progress on renovating the dfx new command.