Skip to content
This repository has been archived by the owner on Jul 6, 2021. It is now read-only.

next-css update #569

Closed
michu2k opened this issue Nov 18, 2019 · 8 comments
Closed

next-css update #569

michu2k opened this issue Nov 18, 2019 · 8 comments

Comments

@michu2k
Copy link

michu2k commented Nov 18, 2019

Hello
Can you please update next-css config & dependencies? A new version of extract-css-chunks-webpack-plugin package is available, which introduces ignoreOrder option and it would be great if this option was available in this plugin.

@ppsirius
Copy link

Last update was 9 months ago :[

@kachkaev
Copy link
Contributor

@michu2k if you are just using css and don't need less/sass, how about trying experimental: { css: true }? See vercel/next.js#8626 and vercel/next.js#8710.

That said, I think it would be valuable to release new versions of next-css, next-less and next-sass plugins. Despite that the built-in support is coming in future, certain scenarios are getting pretty painful today. So a simple dependency update in plugins would be a huge relief to many of us 🙏

@michu2k
Copy link
Author

michu2k commented Nov 22, 2019

Thanks @kachkaev for the answer. I really appreciate your help, but I'm using sass in my project.

@ghost
Copy link

ghost commented Nov 29, 2019

extract-css-chunks-webpack-plugin the latest version is 4.7.1,but in this repos use 3.7.1,this version has some issue likes #174, I fork the project, and fix it in local, but I wish it can be updated

@felixmosh
Copy link

I ended up forking next-css and installing the package from github directly.
:\

@drewlustro
Copy link

Ugh... doesn't look like this is ever going to get an update.

They're fixated on vercel/next.js#8626 :(

@timneutkens
Copy link
Member

Hi, thanks for creating an issue. We currently recommend using https://nextjs.org/docs/basic-features/built-in-css-support as the plugins have been deprecated in favor of the built-in support.

@kachkaev
Copy link
Contributor

@timneutkens unfortunately we still need plugins for projects using less. It’d be great to get some attention to these, which would involve upgrades to the plugins. I know that using CSS modules or styled-components is better, but it’s not always possible.

An example of a hard dependency on less is ant design. That library is very popular (55K github stars) and the integration between it and Next is quite painful at the moment. Deprecation of next-css and next-less makes things worse in the long run as they are currently needed for the setup.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants