-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error thrown by LoadRunner.js as part of webpack: callback was already called #32
Comments
Tried simply running the development version with |
After my "success" running When I now run A mystery of software. Not very satisfying, but lessens my immediate need for help. |
And I'm sure you will hate me. ;) After successfully running and changing the message from the Git Bash shell as I previously described, I tried opening the WebStorm appeared to successfully load the project; however, when I run C:\Users\larry.jones\AppData\Roaming\npm\yarn.cmd run build Error: callback(): The callback was already called. Node.js v18.4.0 Process finished with exit code 1 FYI. I see the same error running Additionally, I did just verify that the terminal I have configured for WebStorm is |
And for the continued mystery that is software... Before I "successfully" executed node:internal/crypto/hash:67 Error: error:0308010C:digital envelope routines::unsupported I've run into this before trying to run tutorials based on older versions of Nodejs. The fix that I employed previously and used again was to set an environment variable, When I added this environment variable to my WebStorm build configuration, everything worked again. I suspect it would work in WebStorm from the terminal if I set this variable also. With apologies to the writers of the movie, "Clue," and probably others, perhaps "'callback already called' is just a red herring." |
I was just going through The Elmish Book too (on a Mac) and encountered the same error you saw in LoadRunner.js. I dug around and found this Stack Overflow post: https://stackoverflow.com/questions/66028314/error-node-modules-callback-was-already-called I ended up doing
And it gave me a new error:
Which apparently affects only Apple silicon... I then dug into that issue and found an issue on Fable's github: fable-compiler/Fable#3239 Apparently fable-loader isn't used anymore, so I ended up following the instructions here to create a new Fable project from scratch: https://fable.io/docs/2-steps/your-first-fable-project.html I figured I could just copy-paste the code from The Elmish Book into it. Well, I eventually ran into yet another problem when I run
I also did the |
Platform: Windows 10
Shell: Git Bash for Windows (with zsh)
Nodejs: v18.4.0
fable-compiler: 2.13.0
I am trying to run through the code examples from "The Elmish Book". (Thank you very much for this book. Reading it really helps understand what's going on.)
I cloned this repository, removed the .git directory (since I have a "parent" local git repository already), and then executed
npm install
. Installing packages succeeded with warnings and some audit flags.I then ran
npm run build
and encountered an error I'm at loss to investigate. Here's my shell output:larry.jones in fable-getting-started on laj/proto/use-npm
λ npm run build
fable-compiler 2.13.0
fable: Compiled src\App.fsproj
C:\Users\larry.jones\professional\projects\the-elmish-book\fable-getting-started\node_modules\loader-runner\lib\LoaderRunner.js:106
throw new Error("callback(): The callback was already called.");
^
Error: callback(): The callback was already called.
at context.callback (C:\Users\larry.jones\professional\projects\the-elmish-book\fable-getting-started\node_modules\loader-runner\lib\LoaderRunner.js:106:10)
at C:\Users\larry.jones\professional\projects\the-elmish-book\fable-getting-started\node_modules\fable-loader\index.js:147:9
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Node.js v18.4.0
I've joined the F# Software Foundation and am awaiting my invitation to the slack channel, but thought this repository might be an appropriate place to raise this issue.
Thanks.
P.S. My first set of steps, which produced the same error, involved deleting the node_modules directory and package-lock.json and running
yarn install
. This start eventually led to the same error.The text was updated successfully, but these errors were encountered: