Support numeric separators
See original GitHub issueNumeric separators proposal is now in Stage 4.
https://github.com/tc39/proposal-numeric-separator
ESLint’s default parser will support this syntax under ecmaVersion: 2021
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Numeric separators (`1_000_000_000_000`) - CanIUse
"Can I use" provides up-to-date browser support tables for support of front-end web technologies on ... grammar: Numeric separators ( 1_000_000_000_000 ).
Read more >Support for numeric separators in acorn - GitHub
Numeric separator support for Acorn. NPM version. This is a plugin for Acorn - a tiny, fast JavaScript parser, written completely in JavaScript....
Read more >babel/plugin-proposal-numeric-separator
@babel/plugin-proposal-numeric-separator. NOTE: This plugin is included in @babel/preset-env , in ES2021 ... No real benefit with separators here.
Read more >Numeric separators - V8 JavaScript engine
JavaScript now supports underscores as separators in numeric literals, increasing readability and maintainability of source code.
Read more >Numeric Separators in JavaScript - DEV Community
Numeric Separators in javascript, enables underscore as a separator in numeric literals to improve readability. Example: let series = 1_00_00;.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems there’s an agreement to split PRs.
I’m working on a PR for the rest of the changes related to numeric separators.
I prefer smaller PRs, personally 😃 As long as folks aren’t touching the same code, we should be able to release Espree and then bump the version in individual PRs. When they’re all ready and approved, we can merge them in, rebasing the latter ones on the first.