Updating to 3.2 breaks tailwind integration in production

[razzeee]

Updating to 3.2 breaks tailwind integration in production

[slorber]

Thanks for reporting, it's probably a mistake I did when refactoring things to improve performance.

I'll take a look soon and publish a fix ASAP.

[Airkro]

When using v3.2.0, plugins.configurePostCss(options) api not work anymore, maybe is the reason.

[slorber]

Fix released in v3.2.1

https://github.com/facebook/docusaurus/releases/tag/v3.2.1

[Arhell]

I don't have any problem with Docusaurus V2 in this sandbox following this guide

https://stackblitz.com/edit/github-fvf5eb?file=src%2Fpages%2Findex.js

Thanks for the example, but it’s not very clear why everything works in the https://openfeature.dev/ version. https://github.com/open-feature/openfeature.dev/blob/main/docusaurus.config.ts#L279

And after updating the dependencies there are no open-feature/openfeature.dev#489

Although, as mentioned above, everything works locally, but in production, alas. https://deploy-preview-489--openfeature.netlify.app/

[Arhell]

and this is for all projects where I updated dependencies yesterday
AvaloniaUI/avalonia-docs#436
openyurtio/openyurt.io#405

and everyone has the same problem, locally everything is fine, production is not

[OzakIOne]

Oops my bad, I forgot after trying to reproduce with the base guide the problem is in production

Indeed I have the same error in the sandbox with version 3.2.0 and no issue in version 3.1.0 i'll try to take a look

3.2.0 sanbox dev no issue, prod issue

3.1.0 sandbox dev and prod no issue

[slorber]

Ah, I see yes, it might prevent you from using a canary due to the 0.0.0 versions. I will try to figure out a solution to improve this.

[Arhell]

more example
open-feature/openfeature.dev#489

[SJFCS]

I had the same problem when I upgraded to version 3.2 that will lost tailwind css style after npm build, I look forward to a solution to this problem

[OzakIOne]

I don't have any problem with Docusaurus V3 in this sandbox following this guide

https://stackblitz.com/edit/github-fvf5eb?file=src%2Fpages%2Findex.js

See my comment below

[heysokam]

@slorber I've seen people report that the bug doesn't trigger on v3.1.0
Whatever broke it, it also fails in the same way with v3.1.1
I went back in history in my repository to a commit that I knew for a fact it worked, removed cache and node_modules to start fresh, and the bug still triggers
In fact, it started triggering with that version running without updating to 3.2.0

edit1:
It might be me calling the old repository by accident. I'm double checking, sorry
Will edit this comment again after confirming.

Edit2: Nope, nvm. It is triggering in v3.1.1 indeed
I removed, specifically, /build, /.docusaurus, /node_modules and package-lock.json to start fresh, and it still triggers.
A teammate tested on their computer, which had not updated since a long time ago, or reset anything, and they don't trigger the issue. We are trying to find why that is the case.

Edit3: It was triggering in ^3.1.1 specifically, which installed 3.2.0 for a reason unknown to our team. See my next comment.

[heysokam]

Update: We were on ^3.1.1, but it was rounding up to 3.2.0 on install.
So false alarm, it triggers on v3.2.0, and works correctly in v3.1.0

[slorber]

Can you please test canary 0.0.0-5886?
https://docusaurus.io/community/canary

It is the same as v3.2 (no breaking change, but this problem should be fixed)

[Arhell]

Can you please test canary 0.0.0-5886? https://docusaurus.io/community/canary

It is the same as v3.2 (no breaking change, but this problem should be fixed)

I checked it on all the projects that I support, everything works, only the one had problems with the plugin https://www.npmjs.com/package/docusaurus-plugin-image-zoom

but I think this is not a problem, I deleted it and everything worked, most likely it does not support the canary version or there is another problem.

Thanks for the work.

[razzeee]

Canary seems to work for me too - but I also had to remove a dependency, cause it was expecting a docusaurus version bigger then 3.0

[slorber]

Great 👍

I'll release soon

everything works, only the one had problems with the plugin npmjs.com/package/docusaurus-plugin-image-zoom

Maybe worth opening an issue on that plugin repo. I can't help if I don't know what the problem was.

Canary seems to work for me too - but I also had to remove a dependency, cause it was expecting a docusaurus version bigger then 3.0

Which dependency? Which version are you upgrading from? 2.x?

[razzeee]

Canary seems to work for me too - but I also had to remove a dependency, cause it was expecting a docusaurus version bigger then 3.0

Which dependency? Which version are you upgrading from? 2.x?

Docusaurus 3.2 to the canary

Dependency is docusaurus-plugin-search-local

Probably caused by https://github.com/gabrielcsapo/docusaurus-plugin-search-local/blob/main/package.json#L97