Open seaders opened 7 months ago
I also experienced this error. Thanks for the nice investigation, downgrading to date-fns 3.1.0 also saved my Plasmo production build! In development mode somehow everything works as expected, even with date-fns 3.6.0.
What happened?
We use an external library,
date-fns
https://github.com/date-fns/date-fns/issues/3670 and when we updated to version 3.2.0 of it, it stopped working, and broke our app in quite a few different places. I opened the above bug with them, and created a simple sample project to show the breakage, https://github.com/seaders/date-fns-example .They are going to check to see if something's wrong on their side, but from their perspective, the plasmo build is building incorrectly - all works fine in a vanilla react project.
When the dev from![image](https://github.com/PlasmoHQ/plasmo/assets/955114/9e391e8d-55f7-468b-9ff8-9a30a7b3074d)
date-fns
had a look, this is where they specifically noticed,Again, they'll take a look at what they may be doing incorrectly to cause this their side, but their initial consideration is that it's a bug with plasmo.
Version
Latest
What OS are you seeing the problem on?
MacOSX
What browsers are you seeing the problem on?
Chrome
Relevant log output
(OPTIONAL) Contribution
Code of Conduct