2009-12-24 17:41:35 -05:00
|
|
|
{
|
2017-02-12 20:00:05 -05:00
|
|
|
"name": "coffeescript",
|
2014-01-27 20:56:29 -05:00
|
|
|
"description": "Unfancy JavaScript",
|
|
|
|
"keywords": [
|
|
|
|
"javascript",
|
|
|
|
"language",
|
|
|
|
"coffeescript",
|
|
|
|
"compiler"
|
|
|
|
],
|
|
|
|
"author": "Jeremy Ashkenas",
|
2018-03-11 16:48:14 -04:00
|
|
|
"version": "2.2.3",
|
2014-01-27 20:56:29 -05:00
|
|
|
"license": "MIT",
|
|
|
|
"engines": {
|
2017-09-01 15:19:15 -04:00
|
|
|
"node": ">=6"
|
2011-02-17 21:21:31 -05:00
|
|
|
},
|
2014-01-27 20:56:29 -05:00
|
|
|
"directories": {
|
2017-02-12 20:00:05 -05:00
|
|
|
"lib": "./lib/coffeescript"
|
2011-02-17 21:21:31 -05:00
|
|
|
},
|
2017-05-14 00:18:05 -04:00
|
|
|
"main": "./lib/coffeescript/index",
|
|
|
|
"browser": "./lib/coffeescript/browser",
|
2014-01-27 20:56:29 -05:00
|
|
|
"bin": {
|
|
|
|
"coffee": "./bin/coffee",
|
|
|
|
"cake": "./bin/cake"
|
2011-02-17 21:21:31 -05:00
|
|
|
},
|
2016-09-24 08:26:46 -04:00
|
|
|
"files": [
|
|
|
|
"bin",
|
|
|
|
"lib",
|
|
|
|
"register.js",
|
|
|
|
"repl.js"
|
|
|
|
],
|
2012-07-08 22:55:43 -04:00
|
|
|
"scripts": {
|
2016-11-29 02:10:17 -05:00
|
|
|
"test": "node ./bin/cake test",
|
2013-11-29 23:59:22 -05:00
|
|
|
"test-harmony": "node --harmony ./bin/cake test"
|
2012-07-08 22:55:43 -04:00
|
|
|
},
|
2014-01-27 20:56:29 -05:00
|
|
|
"homepage": "http://coffeescript.org",
|
2014-05-08 15:07:42 -04:00
|
|
|
"bugs": "https://github.com/jashkenas/coffeescript/issues",
|
2014-01-27 20:56:29 -05:00
|
|
|
"repository": {
|
2011-02-17 21:21:31 -05:00
|
|
|
"type": "git",
|
2014-05-08 15:07:42 -04:00
|
|
|
"url": "git://github.com/jashkenas/coffeescript.git"
|
2011-08-04 23:55:48 -04:00
|
|
|
},
|
|
|
|
"devDependencies": {
|
2017-09-02 15:48:38 -04:00
|
|
|
"babel-core": "~6.26.0",
|
[CS2] Comments (#4572)
* Make `addLocationDataFn` more DRY
* Style fixes
* Provide access to full parser inside our custom function running in parser.js; rename the function to lay the groundwork for adding data aside from location data
* Fix style.
* Fix style.
* Label test comments
* Update grammar to remove comment tokens; update DSL to call new helper function that preserves comments through parsing
* New implementation of compiling block comments: the lexer pulls them out of the token stream, attaching them as a property to a token; the rewriter moves the attachment around so it lives on a token that is destined to make it through to compilation (and in a good placement); and the nodes render the block comment. All tests but one pass (commented out).
* If a comment follows a class declaration, move the comment inside the class body
* Style
* Improve indentation of multiline comments
* Fix indentation for block comments, at least in the cases covered by the one failing test
* Don’t reverse the order of unshifted comments
* Simplify rewriter’s handling of comments, generalizing the special case
* Expand the list of tokens we need to avoid for passing comments through the parser; get some literal tokens to have nodes created for them so that the comments pass through
* Improve comments; fix multiline flag
* Prepare HereComments for processing line comments
* Line comments, first draft: the tests pass, but the line comments aren’t indented and sometimes trail previous lines when they shouldn’t; updated compiler output in following commit
* Updated compiler, now with line comments
* `process` doesn’t exist in the browser, so we should check for its existence first
* Update parser output
* Test that proves #4290 is fixed
* Indent line comments, first pass
* Compiled output with indented line comments
* Comments that start a new line shouldn’t trail; don’t skip comments attached to generated tokens; stop looking for indentation once we hit a newline
* Revised output
* Cleanup
* Split “multiline” line comment tokens, shifting them forward or back as appropriate
* Fix comments in module specifiers
* Abstract attaching comments to a node
* Line comments in interpolated strings
* Line comments can’t be multiline anymore
* Improve handling of blank lines and indentation of following comments that start a new line (i.e. don’t trail)
* Make comments compilation more object-oriented
* Remove lots of dead code that we don’t need anymore because a comment is never a node, only a fragment
* Improve eqJS helper
* Fix #4290 definitively, with improved output for arrays with interspersed block comments
* Add support for line comments output interspersed within arrays
* Fix mistake, don’t lose the variable we’re working on
* Remove redundant replacements
* Check for indentation only from the start of the string
* Indentations in generated JS are always multiples of two spaces (never tabs) so just look for 2+ spaces
* Update package versions; run Babel twice, once for each preset, temporarily until a Babili bug is fixed that prevents it from running with the env preset
* Don’t rely on `fragment.type`, which can break when the compiler is minified
* Updated generated docs and browser compiler
* Output block comments after function arguments
* Comments appear above scope `var` declarations; better tracking of generated `JS` tokens created only to shepherd comments through to the output
* Create new FuncGlyph node, to hold comments we want to output near the function parameters
* Block comments between `)` and `->`/`=>` get output between `)` and `{`.
* Fix indentation of comments that are the first line inside a bare mode block
* Updated output
* Full Flow example
* Updated browser compiler
* Abstract and organize comment fragment generation code; store more properties on the comment fragment objects; make `throw` behave like `return`
* Abstract token insertion code
* Add missing locationData to STRING_START token, giving it the locationData of the overall StringWithInterpolations token so that comments attached to STRING_START end up on the StringWithInterpolations node
* Allow `SUPER` tokens to carry comments
* Rescue comments from `Existence` nodes and `If` nodes’ conditions
* Rescue comments after `\` line continuation tokens
* Updated compiled output
* Updated browser compiler
* Output block comments in the same `compileFragments` method as line comments, except for inline block comments
* Comments before splice
* Updated browser compiler
* Track compiledComments as a property of Base, to ensure that it’s not a global variable
* Docs: split up the Usage section
* Docs for type annotations via Flow; updated docs output
* Update regular comments documentation
* Updated browser compiler
* Comments before soak
* Comments before static methods, and probably before `@variable =` (this) assignments generally
* Comments before ‘if exists?’, refactor comment before ‘if this.var’ to be more precise, improve helper methods
* Comments before a method that contains ‘super()’ should output above the method property, not above the ‘super.method()’ call
* Fix missing comments before `if not` (i.e. before a UNARY token)
* Fix comments before ‘for’; add test for comment before assignment if (fixed in earlier commit)
* Comments within heregexes
* Updated browser compiler
* Update description to reflect what’s now happening in compileCommentFragments
* Preserve blank lines between line comments; output “whitespace-only” line comments as blank lines, rather than `//` following by whitespace
* Better future-proof comments tests
* Comments before object destructuring; abstract method for setting comments aside before compilation
* Handle more cases of comments before or after `for` loop declaration lines
* Fix indentation of comments preceding `for` loops
* Fix comment before splat function parameter
* Catch another RegexWithInterpolations comment edge case
* Updated browser compiler
* Change heregex example to one that’s more readable; update output
* Remove a few last references to the defunct HERECOMMENT token
* Abstract location hash creation into a function
* Improved clarity per code review notes
* Updated browser compiler
2017-08-02 22:34:34 -04:00
|
|
|
"babel-preset-babili": "~0.1.4",
|
2017-12-11 02:12:33 -05:00
|
|
|
"babel-preset-env": "~1.6.1",
|
2018-02-01 23:14:26 -05:00
|
|
|
"babel-preset-minify": "^0.3.0",
|
2018-02-22 03:31:14 -05:00
|
|
|
"codemirror": "^5.35.0",
|
2018-02-01 23:14:26 -05:00
|
|
|
"docco": "~0.8.0",
|
2017-07-17 02:53:22 -04:00
|
|
|
"highlight.js": "~9.12.0",
|
[CS2] Fix CS2 docs mobile issues, improve performance (#4688)
* Get rid of offcanvas slide-in; fix sidebar
* We need to transpile docs.coffee, since Safari 9 throws an error on it and that’s too new a browser not to support; but this should also speed things up
* Fix some tabs
* Fix scrollbar
* Use Highlight.js to format placeholder code (during compilation, not rendering) before CodeMirror loads; match Highlight.js styles to CodeMirror styles as best we can
* Improve hash management
* Initialize CodeMirror on demand, on mouseover a particular code example, rather than all examples on startup
* Replace highlight.js with Prism for placeholder syntax highlighting
* Scratch Prism, use CodeMirror itself to do Node-based syntax highlighting, so that on CodeMirror initialization there’s no flash from mismatched highlighting
* Update packages; there’s a new version of Jison! (doesn’t change much)
* Fix mobile issues: use SVG play button icon, to avoid iOS blue square play button; make the code editor text 16px size explicit, to avoid unwanted mobile zoom; make the ‘code play’ buttons work even if the code examples are in placeholder (non-editable) mode, in case a user hasn’t moused over/tapped them
* Update docs output
* Whoops, CodeMirror is only a devDependency
2017-09-07 11:01:12 -04:00
|
|
|
"jison": ">=0.4.18",
|
2018-02-22 03:31:14 -05:00
|
|
|
"markdown-it": "~8.4.1",
|
2017-05-14 00:18:05 -04:00
|
|
|
"underscore": "~1.8.3",
|
2018-03-11 16:48:14 -04:00
|
|
|
"webpack": "~4.1.1"
|
2016-10-23 11:37:51 -04:00
|
|
|
},
|
2017-04-18 02:30:40 -04:00
|
|
|
"dependencies": {}
|
2009-12-24 17:41:35 -05:00
|
|
|
}
|