fisker Cheung
fisker Cheung
Flow version: 0.202.0 ## Expected behavior ```console > require('flow-parser').parse('#!/usr/bin/env node\n', {tokens: true}) \node_modules\flow-parser\flow_parser.js:807 throw a}function ^ Error: Internal error: Offset_utils.Offset_lookup_failed(_, "Failure while looking up column. Index: -1. Length: 1.") ```...
Flow version: 0.138.0 ## Expected behavior When parsing `" a "`, other parsers like `babel`/`espree`(EDIT: espree has `{start:0, end:3, range: [1,2]}`)/`acorn` returns `Program.range` equals to `[0, 3]` ## Actual behavior...
```js /[$@]?[a-zA-Z_\u0080-\uFFFF][\w\-\u0080-\uFFFF]*/g ``` Should optimize to ```diff - /[$@]?[A-Z_a-z\u0080-\uFFFF][\w\u0080-\uFFFF\-]*/g + /[$@]?[A-Z_a-z\u0080-\uFFFF][\w\u0080-\uFFFF-]*/g ``` Found in https://github.com/prettier/prettier/pull/7991/files#diff-855523a43e898c253460fcf0f6e5f2a1R980
I don't understand how it conflicts with Prettier. It's been enabled in Prettier codebase since the rule released. https://github.com/prettier/prettier/pull/12469 I never see any conflicts. Quote from https://github.com/prettier/eslint-config-prettier/pull/269#issuecomment-1807580963 > Sure, here,...
```bash require('postcss-selector-parser')().processSync('[#{$Keep}]') ``` should be ```diff -'[#{Keep}]' +'[#{$Keep}]' ```
`[email protected]` has been released for a while, it will be great if we can support that. https://github.com/eemeli/yaml/releases
Adapt the banner to dark mode It can auto switch to dark mode, but currently not working in chrome, https://bugs.chromium.org/p/chromium/issues/detail?id=1093736, but at least offer users already in dark mode a...
Sometimes it's useful to attach additional information to the error, so I use `throw Object.assign(Error('...'), ...)`. `throw-new-error` should report on this use case. I haven't checked, but other error related...