René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"\"Parsing error\" when using Yarn 2.0's Plug 'n' Play","articleBody":"I just migrated to Yarn 2.0 and enabled PnP. Got our webpack + babel + TypeScript pipeline up and running. Eslint, however, both when run through the CLI and as part of Webpack, throws OOM errors. Running eslint with --debug, I could see that something in the plugin chain throws an error and if you get enough of them, a generic OOM triggers. Basically all files being checked throw this error.\r\n\r\n**What did you expect to happen?**\r\n\r\nBeing able to run eslint w/ `@typescript-eslint/plugin` on our TypeScript code base.\r\n\r\n**What actually happened?**\r\n\r\n```\r\neslint:cli-engine Lint [redacted]\\wwwroot\\app\\helpers.ts +0ms\r\n  eslint:linter Linting code for [redacted]\\wwwroot\\app\\helpers.ts (pass 1) +0ms\r\n  eslint:linter Verify +0ms\r\n  eslint:linter With ConfigArray: [redacted]\\wwwroot\\app\\helpers.ts +1ms\r\n  eslint:linter Parsing error: Cannot destructure property `name` of 'undefined' or 'null'.\r\n  eslint:linter TypeError: Cannot destructure property `name` of 'undefined' or 'null'.\r\n    at getPackageInformation ([redacted]\\.pnp.js:29078:33)\r\n    at Object.getPackageInformation ([redacted]\\.pnp.js:29398:20)\r\n    at getPnpTypeRoots ([redacted]\\.yarn\\cache\\typescript-patch-fea84800fa-1.zip\\node_modules\\typescript\\lib\\typescript.js:27922:42)\r\n    at getDefaultTypeRoots ([redacted]\\.yarn\\cache\\typescript-patch-fea84800fa-1.zip\\node_modules\\typescript\\lib\\typescript.js:27938:24)\r\n    at getEffectiveTypeRoots ([redacted]\\.yarn\\cache\\typescript-patch-fea84800fa-1.zip\\node_modules\\typescript\\lib\\typescript.js:27893:20)\r\n    at Object.getAutomaticTypeDirectiveNames ([redacted]\\.yarn\\cache\\typescript-patch-fea84800fa-1.zip\\node_modules\\typescript\\lib\\typescript.js:28068:29)\r\n    at Object.createProgram ([redacted]\\.yarn\\cache\\typescript-patch-fea84800fa-1.zip\\node_modules\\typescript\\lib\\typescript.js:95251:56)\r\n    at Object.getBuilderCreationParameters ([redacted]\\.yarn\\cache\\typescript-patch-fea84800fa-1.zip\\node_modules\\typescript\\lib\\typescript.js:98523:29)\r\n    at createSemanticDiagnosticsBuilderProgram ([redacted]\\.yarn\\cache\\typescript-patch-fea84800fa-1.zip\\node_modules\\typescript\\lib\\typescript.js:98839:100)\r\n    at createNewProgram ([redacted]\\.yarn\\cache\\typescript-patch-fea84800fa-1.zip\\node_modules\\typescript\\lib\\typescript.js:100505:30) +2s\r\n```\r\nI cannot tell if this is a bug in the parser, the plugin, or in the PnP API, or Yarn's bundled patched TypeScript compiler, or a combination. However, disabling `@typescript-eslint/parser` and running the same setup on a `.js` file works fine., so hence why I'm posting it here. I've also disabled all other eslint plugins with no change, so any of those shouldn't be the culprit either.\r\n\r\n**Versions**\r\n\r\n| package                     | version |\r\n| --------------------------- | ------- |\r\n| `@typescript-eslint/parser` | `2.19.2` |\r\n| `TypeScript`                | `3.7.5` * |\r\n| `babel`                | `7.8.4` |\r\n| `ESLint`                    | `6.8.0` |\r\n| `node`                      | `10.16.3` |\r\n| `yarn`                       | `2.0.0-rc28` |\r\n*: only used for manually invoking a project-wide type-checking from the CLI (works perfectly fine), otherwise Babel is doing the transpiling","author":{"url":"https://github.com/jstaro","@type":"Person","name":"jstaro"},"datePublished":"2020-02-11T15:32:52Z","url":"https://github.com/typescript-eslint/typescript-eslint/issues/1592"}