Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run tsconfig paths resolver before PnP #12104

Merged

Conversation

timneutkens
Copy link
Member

Based on #11293 (comment)

Not sure how to test PnP and couldn't figure out how to debug packages installed through PnP. We'll have to update this either way as PnP is going to be built into webpack 5 and that would change the order to be like this too.

Based on vercel#11293 (comment)

Not sure how to test PnP and couldn't figure out how to debug packages installed through PnP. We'll have to update this either way as PnP is going to be built into webpack 5 and that would change the order to be like this too.
@arcanis
Copy link
Contributor

arcanis commented Apr 22, 2020

couldn't figure out how to debug packages installed through PnP.

Quick note: you can just run yarn unplug next, and .yarn/unplugged/next-*/ will be updated to contain the next sources that you can edit at will. Same thing with any other package (for example yarn unplug enhanced-resolve, etc).

@timneutkens
Copy link
Member Author

@arcanis thanks! That'll definitely help in the future 🙏

@timneutkens timneutkens merged commit 555ba60 into vercel:canary Apr 24, 2020
@timneutkens timneutkens deleted the fix/pnp-resolving-issue-with-paths branch April 24, 2020 13:50
rokinsky pushed a commit to rokinsky/next.js that referenced this pull request Jul 11, 2020
@vercel vercel locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants