Toru Nagashima

Hmm. This package doesn't depend on `process/browser` in production builds. I suspect that your webpack.config.js has a problem.

Thank you for this issue. Yes, it will be good if this parser can parse pug. But I don't have knowledge about pug syntax and semantics, so I don't have...

@lehni Thank you! You are right. That `pug-lexer` looks good starting point. I image the steps are below: 1. Parse the inside of `` with `pug-lexer`. 2. Convert the result...

- Making AST nodes and tokens is in https://github.com/mysticatea/vue-eslint-parser/tree/da877ec63b2314e6ee0e9f7df9b4e4aa3b359bc5/src/html. - Re-parsing for Vue.js directives is in https://github.com/mysticatea/vue-eslint-parser/blob/da877ec63b2314e6ee0e9f7df9b4e4aa3b359bc5/src/html/parser.ts#L386-L398 - Re-parsing for mustaches (e.g. `{{foo}}`) is https://github.com/mysticatea/vue-eslint-parser/blob/da877ec63b2314e6ee0e9f7df9b4e4aa3b359bc5/src/html/parser.ts#L555

Thank you for your report. However, this is intentional. If you don't care about the future versions, you can disable `node/no-deprecated-api` rule safely. Because existing APIs are never removed without...

You can use a third-party package (e.g., [whatwg-url](https://www.npmjs.com/package/whatwg-url)) or just disable the rule by `eslint-disable` comment with the reason.

No. That's false negative. If you don't mind the deprecated feature in the future versions, you can disable this rule safely, because Node.js doesn't remove those in the major version...

Thank you for the report. This is a bug of ESLint (eslint/eslint#11510) and has been fixed on master (eslint/eslint#11546). For now, please use one of workarounds: - Use `plugin:node/recommended-script` or...

At least, I'm using those rules for private packages as well.

Thank you for your proposal. But `prefer-global/*` rule is very simple and the default is disabled. You can choose to not enable the rule when you use older Node.js.