paralleldrive / paralleldrive/riteway
How to run with nodemon or chokidar?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 40
- Avg merge
- 4h 53m
- Merged PRs (30d)
- 7
Description
Just in case someone needs this - this will keep running riteway as changes are made to the source or test files. Couldn't get it to work with nodemon but chokidar-cli works - it uses chokidar to monitor files and run a command after any changes.
Install chokidar-cli - https://github.com/kimmobrunfeldt/chokidar-cli
npm install --save-dev chokidar-cli
Update the test script in package.json - the --command option specifies the command to run after any of the specified files change, and --initial tells chokidar to run the command once on start -
{
"name": "ta",
"version": "0.1.0",
"scripts": {
"test": "chokidar \"src/**/*.js\" --initial --command \"riteway -r esm src/**/*.test.js | tap-nirvana\""
},
"license": "ISC",
"devDependencies": {
"chokidar-cli": "^2.1.0",
"esm": "^3.2.25",
"riteway": "^6.1.2",
"tap-nirvana": "^1.1.0"
}
}
Then just
npm test
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package.json and inspect the existing test script and project documentation entry points. Run npm test with the chokidar-based command described in the issue to confirm that source or test changes trigger Riteway; done means the supported workflow and its setup are documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience, testing-qa
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100