Skip to content
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

npm start => Error: error:0308010C:digital envelope routines::unsupported #90

Open
tapiov opened this issue Nov 26, 2022 · 1 comment
Open
Labels

Comments

@tapiov
Copy link

tapiov commented Nov 26, 2022

I posted below issue to LLK/scratch-vm. Their response was

"The playground stopped working because the API for loading a project was recently updated."

Since Turbowarp is in active development, I wonder is the API update fix going to be include to Turbowarp in future?


Expected Behavior
npm start would start without error
Scratch VM playground would open a project

Actual Behavior
Emits error and fails to start
Error: error:0308010C:digital envelope routines::unsupported

Steps to Reproduce
Use latest Node-JS LTS 18.12.1 x64
npm start

-- Probably caused by updated Node-JS so trying legacy SSL provider option
set NODE_OPTIONS=--openssl-legacy-provider

npm start
http://127.0.0.1:8073/playground/#119615668 opens
The project doesn't load, unable to change the project in URL or input box
No AST, see attached screenshot

empty

Steps to reproduce the behavior:

Install Node-JS LTS 18.12.1 x64
git clone https://github.com/LLK/scratch-vm.git
cd scratch-vm
npm install
npm start => fails with (error:0308010C:digital envelope routines::unsupported)

set NODE_OPTIONS=--openssl-legacy-provider
npm start
Go to http://127.0.0.1:8073/playground/#119615668

Page screenshot above, run button only loads project 119615668. If changed, it returns to 119615668
Changing the # in URL doesn't load new project
System Details
Chrome Version 107.0.5304.107 (Official Build) (64-bit)

@GarboMuffin
Copy link
Member

Sorry for the delay on this. You are experiencing two issues:

  • modern versions of Node.js require a flag to enable some APIs that the old version of webpack uses
  • project tokens (how the Scratch Team is making unshared projects secure) broke the scratch-vm playground

We don't use the scratch-vm playground and we pin to old Node.js, so this isn't super high priority for us right now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants