Permalink
Commits on Jun 28, 2017
  1. js-tokens v3.0.2

    lydell committed Jun 28, 2017
  2. Note that ES2017 is supported

    lydell committed Jun 28, 2017
  3. Update devDependencies

    lydell committed Jun 28, 2017
Commits on Jan 30, 2017
  1. js-tokens v3.0.1

    lydell committed Jan 30, 2017
  2. Update .gitignore

    lydell committed Jan 30, 2017
  3. Fix matching of ES2015 unicode escapes

    lydell committed Jan 30, 2017
    Example: `\u{123456}`.
    
    I had mistakenly thought that only 1-6 hex digits were allowed between
    the brackets, but _any_ number of hex digits is allowed according to the
    ECMAScript lexical grammar. It is, however, an _early error_ if the
    value of the hex digits is too large, so in practice you never end up
    with more than 6 hex digits unless you have a large amount of leading
    zeroes.
Commits on Jan 11, 2017
  1. js-tokens v3.0.0

    lydell committed Jan 11, 2017
  2. Update readme

    lydell committed Jan 11, 2017
  3. Update devDependencies

    lydell committed Jan 11, 2017
  4. Don't modify the regex: should improve performance in V8

    lydell committed Jan 11, 2017
    http://v8project.blogspot.se/2017/01/speeding-up-v8-regular-expressions.html
    
    > So how can you, as a JavaScript developer, ensure that your RegExps
    > are fast? If you are not interested in hooking into RegExp internals,
    > make sure that neither the RegExp instance, nor its prototype is
    > modified in order to get the best performance:
    >
    > ```js
    > var re = /./g;
    > re.exec('');  // Fast path.
    > re.new_property = 'slow';
    > ```
    
    This module used to export a single regex, with `.matchToToken` bolted
    on, just like in the above example. This commit changes the exports of
    the module to avoid this issue.
    
    Before:
    
    ```js
    import jsTokens from "js-tokens"
    // or:
    var jsTokens = require("js-tokens")
    var matchToToken = jsTokens.matchToToken
    ```
    
    After:
    
    ```js
    import jsTokens, {matchToToken} from "js-tokens"
    // or:
    var jsTokens = require("js-tokens").default
    var matchToToken = require("js-tokens").matchToToken
    ```
    
    Note that this is a breaking change.
    
    Fixes #6.
Commits on Jun 19, 2016
  1. js-tokens v2.0.0

    lydell committed Jun 19, 2016
  2. Add support for ES2016

    lydell committed Jun 19, 2016
  3. Update devDependencies

    lydell committed Jun 19, 2016
Commits on Mar 27, 2016
  1. js-tokens v1.0.3

    lydell committed Mar 27, 2016
  2. Update coffee-script

    lydell committed Mar 27, 2016
  3. Update copyright years

    lydell committed Mar 27, 2016
  4. Update .travis.yml

    lydell committed Mar 27, 2016
  5. Add ECMAScript support notes

    lydell committed Mar 27, 2016
Commits on Oct 18, 2015
  1. js-tokens v1.0.2

    lydell committed Oct 18, 2015
  2. Update .travis.yml

    lydell committed Oct 18, 2015
  3. Merge pull request #3 from zertosh/npmignore

    lydell committed Oct 18, 2015
    Limit npm package contents
Commits on Jun 20, 2015
  1. js-tokens v1.0.1

    lydell committed Jun 20, 2015
  2. Update dev dependencies

    lydell committed Jun 20, 2015
  3. Declare undeclared variable

    lydell committed Jun 20, 2015
Commits on May 1, 2015
  1. Add comparison with esprima

    lydell committed May 1, 2015
  2. Update .travis.yml

    lydell committed May 1, 2015
Commits on Feb 26, 2015
  1. js-tokens v1.0.0

    lydell committed Feb 26, 2015
  2. Don't match "negative numbers" as <number>s

    lydell committed Feb 26, 2015
    There is no such thing as negative number literals; only the unary `-` operator
    followed by a number literal.