Socket
Socket
Sign inDemoInstall

coffeescript

Package Overview
Dependencies
0
Maintainers
3
Versions
73
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

Comparing version 2.5.1 to 2.6.0

2

lib/coffeescript/browser.js

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ // This **Browser** compatibility layer extends core CoffeeScript functions

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ // `cake` is a simplified version of [Make](http://www.gnu.org/software/make/)

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ // CoffeeScript can be used both on the server, as a command-line compiler based

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ // The `coffee` utility. Handles command-line compilation of CoffeeScript

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -42,2 +42,5 @@ // The CoffeeScript parser is generated by [Jison](https://github.com/zaach/jison)

if (action) {
// This code block does string replacements in the generated `parser.js`
// file, replacing the calls to the `LOC` function and other strings as
// listed below.
action = (match = unwrap.exec(action)) ? match[1] : `(${action}())`;

@@ -54,4 +57,29 @@ // All runtime functions we need are defined on `yy`

};
// This code replaces the calls to `LOC` with the `yy.addDataToNode` string
// defined above. The `LOC` function, when used below in the grammar rules,
// is used to make sure that newly created node class objects get correct
// location data assigned to them. By default, the grammar will assign the
// location data spanned by *all* of the tokens on the left (e.g. a string
// such as `'Body TERMINATOR Line'`) to the “top-level” node returned by
// the grammar rule (the function on the right). But for “inner” node class
// objects created by grammar rules, they won’t get correct location data
// assigned to them without adding `LOC`.
// For example, consider the grammar rule `'NEW_TARGET . Property'`, which
// is handled by a function that returns
// `new MetaProperty LOC(1)(new IdentifierLiteral $1), LOC(3)(new Access $3)`.
// The `1` in `LOC(1)` refers to the first token (`NEW_TARGET`) and the `3`
// in `LOC(3)` refers to the third token (`Property`). In order for the
// `new IdentifierLiteral` to get assigned the location data corresponding
// to `new` in the source code, we use
// `LOC(1)(new IdentifierLiteral ...)` to mean “assign the location data of
// the *first* token of this grammar rule (`NEW_TARGET`) to this
// `new IdentifierLiteral`”. The `LOC(3)` means “assign the location data of
// the *third* token of this grammar rule (`Property`) to this
// `new Access`”.
returnsLoc = /^LOC/.test(action);
action = action.replace(/LOC\(([0-9]*)\)/g, getAddDataToNodeFunctionString('$1'));
// A call to `LOC` with two arguments, e.g. `LOC(2,4)`, sets the location
// data for the generated node on both of the referenced tokens (the second
// and fourth in this example).
action = action.replace(/LOC\(([0-9]*),\s*([0-9]*)\)/g, getAddDataToNodeFunctionString('$1', '$2'));

@@ -103,3 +131,3 @@ performActionFunctionString = `$$ = ${getAddDataToNodeFunctionString(1, patternCount, !returnsLoc)}(${action});`;

],
// Block and statements, which make up a line in a body. YieldReturn is a
// Block and statements, which make up a line in a body. FuncDirective is a
// statement, but not included in Statement because that results in an ambiguous

@@ -503,3 +531,3 @@ // grammar.

],
// The **Code** node is the function literal. It's defined by an indented block
// The **Code** node is the function literal. It’s defined by an indented block
// of **Block** preceded by a function arrow, with an optional parameter list.

@@ -701,3 +729,4 @@ Code: [

],
// A "meta-property" access e.g. `new.target`
// A “meta-property” access e.g. `new.target` or `import.meta`, where
// something that looks like a property is referenced on a keyword.
MetaProperty: [

@@ -708,2 +737,7 @@ o('NEW_TARGET . Property',

LOC(3)(new Access($3)));
}),
o('IMPORT_META . Property',
function() {
return new MetaProperty(LOC(1)(new IdentifierLiteral($1)),
LOC(3)(new Access($3)));
})

@@ -1665,3 +1699,3 @@ ],

// The source of a comprehension is an array or object with an optional guard
// clause. If it's an array comprehension, you can also choose to step through
// clause. If it’s an array comprehension, you can also choose to step through
// in fixed-size increments.

@@ -1668,0 +1702,0 @@ ForSource: [

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ // This file contains the common helper functions that we'd like to share among

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ // Node.js Implementation

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ var LONG_FLAG, MULTI_FLAG, OPTIONAL, OptionParser, SHORT_FLAG, buildRule, buildRules, normalizeArguments, repeat,

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ var CoffeeScript, Module, binary, child_process, ext, findExtension, fork, getRootModule, helpers, i, len, loadFile, path, ref;

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ var CoffeeScript, addHistory, addMultilineHandler, fs, getCommandId, merge, nodeREPL, path, replDefaults, runInContext, sawSIGINT, transpile, updateSyntaxError, vm;

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -1103,3 +1103,3 @@ // The CoffeeScript language has a good deal of optional syntax, implicit syntax,

// If preceded by an `IMPLICIT_FUNC`, indicates a function invocation.
IMPLICIT_CALL = ['IDENTIFIER', 'JSX_TAG', 'PROPERTY', 'NUMBER', 'INFINITY', 'NAN', 'STRING', 'STRING_START', 'REGEX', 'REGEX_START', 'JS', 'NEW', 'PARAM_START', 'CLASS', 'IF', 'TRY', 'SWITCH', 'THIS', 'UNDEFINED', 'NULL', 'BOOL', 'UNARY', 'DO', 'DO_IIFE', 'YIELD', 'AWAIT', 'UNARY_MATH', 'SUPER', 'THROW', '@', '->', '=>', '[', '(', '{', '--', '++'];
IMPLICIT_CALL = ['IDENTIFIER', 'JSX_TAG', 'PROPERTY', 'NUMBER', 'INFINITY', 'NAN', 'STRING', 'STRING_START', 'REGEX', 'REGEX_START', 'JS', 'NEW', 'PARAM_START', 'CLASS', 'IF', 'TRY', 'SWITCH', 'THIS', 'DYNAMIC_IMPORT', 'IMPORT_META', 'NEW_TARGET', 'UNDEFINED', 'NULL', 'BOOL', 'UNARY', 'DO', 'DO_IIFE', 'YIELD', 'AWAIT', 'UNARY_MATH', 'SUPER', 'THROW', '@', '->', '=>', '[', '(', '{', '--', '++'];

@@ -1106,0 +1106,0 @@ IMPLICIT_UNSPACED_CALL = ['+', '-'];

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ // The **Scope** class regulates lexical scoping within CoffeeScript. As you

@@ -1,2 +0,2 @@

// Generated by CoffeeScript 2.5.1
// Generated by CoffeeScript 2.6.0
(function() {

@@ -3,0 +3,0 @@ // Source maps allow JavaScript runtimes to match running JavaScript back to

@@ -11,3 +11,3 @@ {

"author": "Jeremy Ashkenas",
"version": "2.5.1",
"version": "2.6.0",
"license": "MIT",

@@ -44,14 +44,14 @@ "engines": {

"devDependencies": {
"@babel/core": "^7.7.7",
"@babel/preset-env": "^7.7.7",
"babel-preset-minify": "^0.5.1",
"codemirror": "^5.50.0",
"docco": "~0.8.0",
"highlight.js": "~9.17.1",
"jison": "^0.4.18",
"markdown-it": "~10.0.0",
"underscore": "~1.9.1",
"webpack": "~4.41.5"
},
"dependencies": {}
"@babel/core": "~7.15.5",
"@babel/preset-env": "~7.15.6",
"babel-preset-minify": "~0.5.1",
"codemirror": "~5.62.3",
"docco": "~0.8.1",
"highlight.js": "~11.2.0",
"jison": "~0.4.18",
"markdown-it": "~12.2.0",
"puppeteer": "~10.2.0",
"underscore": "~1.13.1",
"webpack": "~5.53.0"
}
}

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc