JS API #3551
Comments
Sure. (Altho there are many plugins out there using the Js api, for gulp grunt and stuff like that. Feel free to open an issue on nlz/transforms saying what's wrong with the current one, and ping me there) :-). |
|
(Leaving this one open because we could have a wiki page explaining the JS API, I think -- unless we already have an issue for that) |
|
okay. i'm just trying to add source maps to everything, but most of these processors don't have docs on the JS API. just a list of methods and options would be nice. |
GeoffreyBooth
added a commit
to GeoffreyBooth/coffeescript
that referenced
this issue
May 3, 2017
GeoffreyBooth
added a commit
that referenced
this issue
May 6, 2017
* Docs: named functions and function declarations * No more prototypal `extends`; update docs and example * More comprehensive documentation of the existential operator; closes #1631 * Better document operators, including `from` * No fat arrow class methods anymore * Destructuring shouldn’t say that default values are applied in case of undefined or null * Spinoff generator and async functions into their own sections; reorder things so that the sections on functions come just before classes, and destructuring goes next to the operators (which discuss assignment) * Rewrite “CoffeeScript 2” section, making it less practical and more explanatory; move practical info into “Usage” * Update “Variable Scoping and Lexical Safety” section to remove incorrect reference to Ruby (fixes #2360), add missing details about the safety wrapper, add note about `let`/`const`. * Updated browser compiler * Updated docs * Rewrite Literate CoffeeScript breaking changes * Split apart the “Breaking Changes” and “Unsupported Features” sections into separate sidebar items and files * Add example of `not in`, closes #3281 * Fix words in bold that should be in backticks * Consolidate some breaking changes sections * Add Node API documentation; closes #3551 * Move the chaining documentation out of the changelog into its own section
|
Done in #4536. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
can't implement anything with coffeescript without a public API, and i'm not going to look through the annotated source
unless you wanna help maintain some processors in https://github.com/normalize/transforms.js, @Nami-Doc :D
The text was updated successfully, but these errors were encountered: