You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Node comes with NPM nowadays, so there’s not really a reason to install CoffeeScript the non-NPM way
* The cake documentation tasks should each have build and watch modes following the same form
* Refactor the build tasks to be more foolproof, including the parser unless it’s explicitly excluded
* Abstract out testing built code, to prepare for watching the build task
* Cake task to cut a new release
* cake build:watch, based on https://github.com/GeoffreyBooth/coffeescript-gulp
* Coding style
* Tests shouldn’t write files in a watched folder
* Don’t crash if the REPL test history file is already gone by the time we try to delete it
Use <code>bin/coffee</code> to test your changes,<br>
2586
2586
<code>bin/cake test</code> to run the test suite,<br>
2587
-
<code>bin/cake build</code> to rebuild the CoffeeScript compiler, and<br>
2588
-
<code>bin/cake build:parser</code> to regenerate the Jison parser if you’re working on the grammar.</p>
2589
-
<p><code>git checkout lib && bin/cake build:full</code> is a good command to run when you’re working on the core language. It’ll refresh the lib directory (in case you broke something), build your altered compiler, use that to rebuild itself (a good sanity test) and then run all of the tests. If they pass, there’s a good chance you’ve made a successful change.</p>
2587
+
<code>bin/cake build</code> to rebuild the full CoffeeScript compiler, and<br>
2588
+
<code>bin/cake build:except-parser</code> to recompile much faster if you’re not editing <code>grammar.coffee</code>.</p>
2589
+
<p><code>git checkout lib && bin/cake build:full</code> is a good command to run when you’re working on the core language. It’ll refresh the <code>lib</code> folder (in case you broke something), build your altered compiler, use that to rebuild itself (a good sanity test) and then run all of the tests. If they pass, there’s a good chance you’ve made a successful change.</p>
2590
2590
</li>
2591
2591
<li><ahref="v1/test.html">Browser Tests</a><br>
2592
2592
Run CoffeeScript’s test suite in your current browser.</li>
`bin/cake build` to rebuild the CoffeeScript compiler, and<br>
7
-
`bin/cake build:parser` to regenerate the Jison parser if you’re working on the grammar.
6
+
`bin/cake build` to rebuild the full CoffeeScript compiler, and<br>
7
+
`bin/cake build:except-parser` to recompile much faster if you’re not editing `grammar.coffee`.
8
8
9
-
`git checkout lib && bin/cake build:full` is a good command to run when you’re working on the core language. It’ll refresh the lib directory (in case you broke something), build your altered compiler, use that to rebuild itself (a good sanity test) and then run all of the tests. If they pass, there’s a good chance you’ve made a successful change.
9
+
`git checkout lib && bin/cake build:full` is a good command to run when you’re working on the core language. It’ll refresh the `lib` folder (in case you broke something), build your altered compiler, use that to rebuild itself (a good sanity test) and then run all of the tests. If they pass, there’s a good chance you’ve made a successful change.
0 commit comments