You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dotnet new fable-elmish-react -n memory-palace-frontend -lang f#
Compiling it, yields the following error:
npm install -g esbuild
npm install
npx webpack-dev-server
./src/memory_palace_frontend.fsproj 39 bytes [built] [code generated] [1 error]
ERROR in ./src/memory_palace_frontend.fsproj
Module build failed (from ./node_modules/fable-loader/index.js):
Error: The specified file name or path is too long, or a component of the specified path is too long.
at /Users/mmulji/memory-palace/frontend/node_modules/fable-loader/index.js:98:22
at processTicksAndRejections (node:internal/process/task_queues:96:5)
webpack 5.74.0 compiled with 1 error in 1975 ms
^C<i> [webpack-dev-server] Gracefully shutting down. To force exit, press ^C again. Please wait...
This is strange, the "path is too long" error used to affect packages in node_modules frequently in Windows, but it seems to have been fixed in recent versions. But according to the report you're using macOS so I'm a bit puzzled.
Also, it's interesting the error comes from fable-loader because it's been a while since we don't use it so maybe the fable-elmish-react template hasn't been updated for a while. cc @MangelMaxime
The Fable docs offer some template alternatives that should be more up-to-date, like the Feliz template or the SAFE template.
I am closing this issue because it has been reported for Fable 3, which is out of support now.
Also, it seems like fable-loader is used in the configuration of the project but this was only used with Fable 2, so perhaps the error come from the fact that the configuration is mixed between 2 version of Fable.
Description
I built a new project using
Compiling it, yields the following error:
Repro code
Expected and actual results
Please provide the expected and actual results.
Related information
dotnet fable --version
The text was updated successfully, but these errors were encountered: