did you figure it out @pme123 ? seems like its coming from somewhere inside webpack?
Ok finally I found the time - started from scratch and it worked - I created a simple example project with all the nice stuff from the Slinky starter project and a working Scalably Plotly example: https://github.com/pme123/scalably-slinky-example
cool @pme123 . in the meantime I also added this little demo https://github.com/ScalablyTyped/SlinkyDemos/blob/master/plotly/src/main/scala/demo/Main.scala
Is there a way I can force recompilation of certain npm dependencies? I'm trying to use recharts, but even though my code compiles I get errors like this:
Uncaught TypeError: Cannot read property 'ResponsiveContainer' of undefined
at $c_Ltypings_recharts_components_ResponsiveContainer$.make__Ltypings_recharts_components_ResponsiveContainer$__sjs_js_Array (ResponsiveContainer.scala:40)
at eval (OrderChart.scala:33)
at $c_sjsr_AnonFunction1.apply__O__O (AnonFunctions.scala:27)
at $c_Lslinky_core_FunctionalComponent$.slinky$core$FunctionalComponent$$$anonfun$apply$1__sjs_js_Object__F1__sr_ObjectRef__Lslinky_core_facade_ReactElement (FunctionalComponent.scala:108)
at OrderChart (FunctionalComponent.scala:106)
at renderWithHooks (react-dom.development.js:14803)
at mountIndeterminateComponent (react-dom.development.js:17482)
at beginWork (react-dom.development.js:18596)
at HTMLUnknownElement.callCallback (react-dom.development.js:188)
at Object.invokeGuardedCallbackDev (react-dom.development.js:237)
I just took the SimpleLineChart from the MaterialUI example. And I got it to work on its own, afaik
And I just tried to build my project on my linux machine, and it complains that a certain type isn't part of the materialUICore package... but it works on my Windows Machine :D
typings.materialUiCore.anon.PartialClassNameMapExpansDisabled works fine on windows, but not my linux machine :(
For the former you may want to turn off stReactEnableTreeShaking if you have that enabled for recharts
Should I link my build file?
The recharts error :(
for recharts, first check that the slinky demo repo works for you.
ResponsiveContainerworks there, so there is no particularly good reason why it shouldnt work in another project.
for the linux build issue if it doesnt go away with clean, sbt restart and so on I'll need more info. run
show stConversionOptions in sbt, and also give me the full error message please
But ill report back on the recharts stuff
5e weird thing is that it has worked before
I do really wonder if the material-ui demo chart could be enough, I have been willing to try it for a while
I get the error from a little above, but basically undefined, when I try to render the SimpleLineChart from the materialUI demo project as standalone component. I got the Dashboard bit with the charts rendering last night fine, so I have no idea what’s happening.
@oyvindberg apparently, reloading on a page other than the home doesn't work, was the fix that I pushed deployed? or it be that there is another change needed for the github pages side?
About this, I remember now, the webserver needs to be configured to serve the index when the file is not found, which I have no idea if can be done on gh pages with your current settings
from this issue, people claim that you can create a symlink from the 404.html page to your index, but that wouldn't work for many entrypoints which is how the demos work: isaacs/github#408
But yeah, it must be a config issue
Because it works fine when I run the demo repo
I deleted every single folder that didnt have anything to do with my code
did sbt clean
And then tried to do it all over again :D
@AlexITC I'm struggling with the CI for the demo repo, the builder container doesn't have enough memory to build mui. What it means is that CI will be green if I run
stPublishCache from my computer, but it's not able to publish itself. If you want to update the published demo you need to run dist in sbt and check in the results, which will be on the docs folder
nice @peterstorm :)
also @AlexITC an easy fix for missing history api on github pages would be to use hash routing instead.