Davlatjon Sh comments

Results 176 comments of


                                            Davlatjon Sh

linter: bug in eslint disable comment

@Boshen issue still persists oxlintrc.json ```json { "env": { "es2015": true, "es2020": true, "node": true, "browser": false, "jest": true }, "globals": {}, "rules": { "brace-style": "off", "@stylistic/brace-style": [ "error", "1tbs",...

linter: bug in eslint disable comment

Yes, it is now works

linter: bug in eslint disable comment

Thank you for fix @Boshen

`oxc-parser` NPM package return AST as JS object, not JSON

@overlookmotel Supporting `TypeScript` interfaces for `program` also would be helpful or using as TypeScript object `as const` which returns RAW data as type

`oxc-parser` NPM package return AST as JS object, not JSON

@overlookmotel ## Input ```js const funcString = /** * * @returns {{status: 'success' | 'error'}} */ (async (req, res) => { const var1 = req.headers['X-Telemetry-ID']; const var2 = req.cookies['X-User-ID']; useEffect(()...

`oxc-parser` NPM package return AST as JS object, not JSON

Thank you @overlookmotel if there need any help at JavaScript/TypeScript-side or any testing, i would like to help with that

`oxc-parser` NPM package return AST as JS object, not JSON

@escaton It will work as expected because all values (even dynamic) will be as types so it gets as `1 | 2` for example instead of type number.

`oxc-parser` NPM package return AST as JS object, not JSON

@escaton Seems i don’t understand what you means by dynamic values. please give me example of dynamic values and i will try to use `as const`. i am not pro...

`oxc-parser` NPM package return AST as JS object, not JSON

For such case I don’t know but with for my own project i am did - parse AST - write to JSON file - Import JSON file via import -...

chore(npm): use `bin.sh` for execute

@Conaclos Yes, that way could reduce startup time