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

Monkey patch next-sass and next-less #8944

Merged
merged 5 commits into from
Oct 3, 2019

Conversation

Timer
Copy link
Member

@Timer Timer commented Oct 3, 2019

These two legacy Next.js plugins use poor webpack practices: they define plugins without resolving it themselves.

As a result, the resolution root is unknown by webpack and you get into package hoisting bugs.

To fix this, we emulate the logic these packages should've performed themselves on a best-effort basis.


Fixes vercel/next-plugins#543
Fixes vercel/next-plugins#541

These two Next.js plugins use poor webpack practices: they define plugins without resolving themselves.

As a result, the resolution root is unknown by webpack and you get into package hoisting bugs.

To fix this, we emulate the logic these packages should've performed themselves on a best-effort basis.
@Timer Timer added this to the 9.0.8 milestone Oct 3, 2019
@Timer Timer added Upstream Related to using Next.js with a third-party dependency. (e.g., React, UI/icon libraries, etc.). Type: Bug labels Oct 3, 2019
@timneutkens
Copy link
Member

Could you add a test for this?

@Timer Timer requested a review from timneutkens October 3, 2019 14:00
@Timer Timer merged commit 955ea42 into vercel:canary Oct 3, 2019
@Timer Timer deleted the fix-next-sass-and-less branch October 3, 2019 14:08
@vercel vercel locked as resolved and limited conversation to collaborators Feb 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Upstream Related to using Next.js with a third-party dependency. (e.g., React, UI/icon libraries, etc.).
Projects
None yet
2 participants