Closed MaxWilson closed 4 years ago
Hi @MaxWilson, you scared me! I thought it was because I used a backslash in my path instead of a / for the property directory. Turns out both work.
This happened because the PR I did to add globbing support for the fable compiler was after the current version you have installed, and I didn't get around to updating the package with it until 1.0.
Changing these lines:
"fable-compiler": "^2.4.16",
"fable-loader": "^2.1.8",
to this:
"fable-compiler": "^2",
"fable-loader": "^2",
and doing a npm upgrade
allowed the build to succeed and show the graph.
(Aside: I'm not sure what you mean about backslashes. In the context of dir on windows, forward slash doesn't work with wildcards, only backslash does. Forward slash only works with exact file paths, so 'dir C:/code/saves/.fable/Feliz.Plotly.1.0.1/Props/*.fs' fails.)
Thank you, now I understand the error, and the fix you suggested works for me. Closing the issue.
The paths in the .fsproj
are parsed by the fable compiler to determine what files to look for, I jumped to conclusions that it was because of a backslash instead of forward slash as a potential reason because I knew the feature worked.
Anyways, glad you were able to get it resolved! :)
Description
Adding a reference to Feliz.Plotly causes my project to fail to compile.
Steps to reproduce
Pre-packaged repro is here. Run npm i and then npm start.
Expected behavior
No error, should still show the elmish-getting-started app (since I haven't yet added any code that actually uses Feliz.Plotly).
Additional context
I don't know why fable-loader is saying nothing is there.
Known workaround
Use Feliz.Plotly 0.22.0 instead of 1.0.x.