Commit 28453ff
File tree
- deps/acorn/acorn
- dist
- doc/contributing/maintaining
- src
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1,3 +1,29 @@ | |||
| 1 | + ## 8.11.2 (2023-10-27) | ||
| 2 | + | ||
| 3 | + ### Bug fixes | ||
| 4 | + | ||
| 5 | + Fix a bug that caused regular expressions after colon tokens to not be properly tokenized in some circumstances. | ||
| 6 | + | ||
| 7 | + ## 8.11.1 (2023-10-26) | ||
| 8 | + | ||
| 9 | + ### Bug fixes | ||
| 10 | + | ||
| 11 | + Fix a regression where `onToken` would receive 'name' tokens for 'new' keyword tokens. | ||
| 12 | + | ||
| 13 | + ## 8.11.0 (2023-10-26) | ||
| 14 | + | ||
| 15 | + ### Bug fixes | ||
| 16 | + | ||
| 17 | + Fix an issue where tokenizing (without parsing) an object literal with a property named `class` or `function` could, in some circumstance, put the tokenizer into an invalid state. | ||
| 18 | + | ||
| 19 | + Fix an issue where a slash after a call to a propery named the same as some keywords would be tokenized as a regular expression. | ||
| 20 | + | ||
| 21 | + ### New features | ||
| 22 | + | ||
| 23 | + Upgrade to Unicode 15.1. | ||
| 24 | + | ||
| 25 | + Use a set of new, much more precise, TypeScript types. | ||
| 26 | + | ||
| 1 | 27 | ## 8.10.0 (2023-07-05) | |
| 2 | 28 | ||
| 3 | 29 | ### New features | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -9,9 +9,7 @@ Acorn is open source software released under an | |||
| 9 | 9 | ||
| 10 | 10 | You are welcome to | |
| 11 | 11 | [report bugs](https://github.com/acornjs/acorn/issues) or create pull | |
| 12 | - requests on [github](https://github.com/acornjs/acorn). For questions | ||
| 13 | - and discussion, please use the | ||
| 14 | - [Tern discussion forum](https://discuss.ternjs.net). | ||
| 12 | + requests on [github](https://github.com/acornjs/acorn). | ||
| 15 | 13 | ||
| 16 | 14 | ## Installation | |
| 17 | 15 | ||
@@ -204,6 +202,13 @@ option is enabled). When the token's type is `tokTypes.eof`, you | |||
| 204 | 202 | should stop calling the method, since it will keep returning that same | |
| 205 | 203 | token forever. | |
| 206 | 204 | ||
| 205 | + Note that tokenizing JavaScript without parsing it is, in modern | ||
| 206 | + versions of the language, not really possible due to the way syntax is | ||
| 207 | + overloaded in ways that can only be disambiguated by the parse | ||
| 208 | + context. This package applies a bunch of heuristics to try and do a | ||
| 209 | + reasonable job, but you are advised to use `parse` with the `onToken` | ||
| 210 | + option instead of this. | ||
| 211 | + | ||
| 207 | 212 | In ES6 environment, returned result can be used as any other | |
| 208 | 213 | protocol-compliant iterable: | |
| 209 | 214 | ||
0 commit comments