-
-
Notifications
You must be signed in to change notification settings - Fork 866
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
feat(razzle): add Yarn PnP support #1398
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/jared/razzle/7cyafnksh |
Great work, but. Can you do this against the next-awesome branch? |
Also, don't format the code. Makes it easier to see the changes. :) |
These changes (except the PnP plugin) are bugfixes that should go out in the current release. Based on #1377
Reverted, but master should probably be formatted then so contributors can make sure their PR is consistent easily |
Isn't the code formatted on commit? Prettier is listed in |
The pattern wasn't matching anything, fixed. |
Next-awesome will support both webpack 4 and 5. I will do a 3.2 off next-awesome before 4.0 without webpack 5. Then add wepback 5 support and some breakIng changes. So I don’t have to keep two brances in sync. Strange, pre commit hook does not run for me. |
But I can lint master 😀 |
It runs for me but it doesn't match any files, with 0eea6ab it matches correctly |
Hm, github desktop does not run pre-commit. But I wont add pnp to master now. It must go in next-awesome. |
I was going to do it just haven't had the time yet, but it's fine, will you add me as a co-author before you merge it? |
I will :)
…On Thu, 27 Aug 2020 at 21:33, Kristoffer K. ***@***.***> wrote:
Closed #1398 <#1398>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1398 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAADGQMXAYNSVJP4ZNJ6ELSC2YGZANCNFSM4QK5566Q>
.
--
Øyvind Saltvik
|
What kind of changes are needed that require upstream changes for plugins? |
When I tested the typescript plugin the upstream dependencies have undeclared dependencies so that needs to be fixed, otherwise it probably works |
What's the problem this PR addresses?
razzle
doesn't work with Yarn PnP due to missing dependencies and incorrect assumptions about thenode_modules
layout.ref #896
How did you fix it?
require.resolve
things that the user isn't responsible for providingNotes
This only adds PnP support to
razzle
, the various plugins haven't been fixed as some of them require upstream changes