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

Postcss-resolve-url: postcss.plugin was deprecated #32157

Closed
JameelKhan9 opened this issue Dec 6, 2021 · 5 comments · Fixed by #32932
Closed

Postcss-resolve-url: postcss.plugin was deprecated #32157

JameelKhan9 opened this issue Dec 6, 2021 · 5 comments · Fixed by #32932
Labels
Webpack Related to Webpack with Next.js.

Comments

@JameelKhan9
Copy link

What version of Next.js are you using?

12.0.7

What version of Node.js are you using?

16.13.0

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

next dev, next build

Describe the Bug

Afer upgrading from 12.0.4 to 12.0.7, the following message appears when yarn dev or yarn build && yarn start:

postcss-resolve-url: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration

Expected Behavior

The deprecation warning does not show.

To Reproduce

  1. checkout next.js/examples/with-next-sass greater than 12.0.4
  2. Run yarn
  3. Run yarn dev
$ > yarn dev                  
yarn run v1.22.17
$ next
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
postcss-resolve-url: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
event - compiled client and server successfully in 1448 ms (171 modules)
@JameelKhan9 JameelKhan9 added the bug Issue was opened via the bug report template. label Dec 6, 2021
@timneutkens timneutkens added kind: bug Webpack Related to Webpack with Next.js. and removed bug Issue was opened via the bug report template. labels Dec 6, 2021
@timneutkens
Copy link
Member

Related to #31762. This is just a warning and will not affect running your app so it's safe to ignore until it's fixed in Next.js.

@tonytoth
Copy link

tonytoth commented Dec 6, 2021

@timneutkens it is affecting the application.
Screenshot 2021-12-06 at 14 43 20

@brc-dd
Copy link

brc-dd commented Dec 6, 2021

@tonytoth Your error is different from what JameelKhan9 wrote. Also, it is not reproducible by the steps given by them. Please provide a minimal, reproducible example. Next.js is already using postcss@8.2.15, so the error in your case most probably has to do something with your own setup.

@ZauJulio

This comment has been minimized.

timneutkens added a commit to timneutkens/next.js that referenced this issue Jan 1, 2022
Fixes vercel#32157

Moves resolve-url-loader into Next.js and strips out all features that are not used like `rework` support. Will reduce install size as well as allow for optimizing the approach in the near future.
ijjk pushed a commit that referenced this issue Jan 2, 2022
* Move resolve-url-loader into Next.js

Fixes #32157

Moves resolve-url-loader into Next.js and strips out all features that are not used like `rework` support. Will reduce install size as well as allow for optimizing the approach in the near future.

* Update precompiled

* Use loader-utils 2

* Update trace test

* Revert "Update trace test"

This reverts commit 7c09a07.

* Add es5-ext as it's used in trace tests

* Update join-function.js

* Update bundle5.js
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Feb 1, 2022
natew pushed a commit to natew/next.js that referenced this issue Feb 16, 2022
* Move resolve-url-loader into Next.js

Fixes vercel#32157

Moves resolve-url-loader into Next.js and strips out all features that are not used like `rework` support. Will reduce install size as well as allow for optimizing the approach in the near future.

* Update precompiled

* Use loader-utils 2

* Update trace test

* Revert "Update trace test"

This reverts commit 7c09a07.

* Add es5-ext as it's used in trace tests

* Update join-function.js

* Update bundle5.js
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Webpack Related to Webpack with Next.js.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants