René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add new moduleResolution option: `yarn-pnp`","articleBody":"## Search Terms\r\n\r\nyarn pnp plug'n'play plug \r\n\r\n## Suggestion\r\n\r\nYarn has released a new feature for using modules without having a `node_modules` directory present: plug'n'play. Some community tooling is available for customizing the TypeScript compilerHost so that it can use plug'n'play modules, but this does not work for users of `tsc`. \r\n\r\nMy suggestion is to add a new `\"moduleResolution\": \"yarnpnp\"` option.\r\n\r\n## Use Cases / Examples\r\n\r\nI want to be able to use yarn plug-n-play in my typescript projects. My projects are typically yarn monorepos where common libraries are basic node packages using `tsc` for compilation. This would allow the basic projects to continue using `tsc`, but with an alternative module resolution scheme.\r\n\r\nSome community tooling has been created here for augmenting the CompileHost with a slightly updated moduleResolution strategy, but using it in basic projects would probably require a forked `tsc`.\r\n\r\nhttps://github.com/arcanis/ts-pnp\r\n\r\n## Checklist\r\n\r\nMy suggestion meets these guidelines:\r\n* [x] This wouldn't be a breaking change in existing TypeScript / JavaScript code\r\n* [x] This wouldn't change the runtime behavior of existing JavaScript code\r\n* [x] This could be implemented without emitting different JS based on the types of the expressions\r\n* [x] This isn't a runtime feature (e.g. new expression-level syntax)\r\n\r\n","author":{"url":"https://github.com/darthtrevino","@type":"Person","name":"darthtrevino"},"datePublished":"2018-11-01T18:57:47Z","url":"https://github.com/microsoft/TypeScript/issues/28289"}