Converting circular structure to JSON #3317
Unanswered
robbykrlos
asked this question in
Q&A
Replies: 1 comment
-
PS: I've opened a question on stackoverflow too: https://stackoverflow.com/questions/73388144/converting-circular-structure-to-json-webpack-apexcharts |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm getting this error on
yarn serve
(while yarn is still processing...):or somethimes yarn crashes entirely with :
Context
I have one project, SPA(
laravel-enso
), VueJs. In thedevelop
branch, we do not haveapexcharts
installed and integrated. in theupgrade
branch we have apexcharts installed:client/package.json
In the
upgrade
branch I have one vue component calledRrdGraph
that makes use ofapexcharts
:Initially the error was very generic and I looked into
package.json
dependencies and if there are circular references. But I saw no issues with the dependencies of eitherapexcharts
orvue3-apexcharts
.I've also observer that
yarn build
was working and onlyyarn serve
was not. Looking deeper into whatbuild
andserve
were doing, I saw that the--mode development
was the only difference that was generating the error.One important fact, that made me think this is related to
apexcharts
was that on thedevelop
branchyarn serve
was not generating this error.I started a long process of divide et impera (divide and conquer) by removing bits from my
RrdGraph
component that usedapexcharts
.I removed and removed, each time checking what part of the code was generating the error, and which removed part was not generating the error.
I reached this part:
If I removed this part. Yarn was working, no errors.
I figured that if I remove the lines with bar options that are default values anyways, it is working - like this:
(these being the only actual changes that we wanted that are not default values)
I thought that was it.
But then, the next one hit me harder:
We changed some comments in these options, so instead of
//Total / 1
we changed it to//New (Total) / 1
This made
yarn serve
crash again.Interestingly, it was only the first comment within
markers
, not the one withinstroke
that made it crash.Conclusion: I have no idea what is happening and why it behaves like this.
It might be also something related to
webpack
.It might be something related to how the options are passed to the component or, how this is converted to JSON in the
--mode development
, but something is strange and am wondering if someone had this issue or could give me some clues...Beta Was this translation helpful? Give feedback.
All reactions