Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This switches the
yarn
linker to PnP. The impetus is to avoid this problem: yarnpkg/yarn#8540 (comment)(CRA sets restrictions on what aliases can be used within webpack, so I wasn't able to get the webpack workaround to work.)
There are a few side-effects of this change:
yarn
's version of things as per https://yarnpkg.com/getting-started/editor-sdkseslint-plugin-import
needs to use https://yarnpkg.com/features/pnp#fallback-mode as per https://psidium.github.io/lerna/monorepo/yarn/nodejs/pnp/zero-install/2021/08/23/migrating-a-monorepo-from-lerna-to-yarn-3.htmltsx
doesn't work with PnP on Node 18 until feat(esm): leverage loaders when resolving subsequent loaders nodejs/node#43772 is backported, so this switches the example package away fromtsx
peerDependencies
intopostcss-loader
viapackageExtensions