LivelyKernel / LivelyKernel/lively.next

install uses deprecated node --no-experimental-fetch

Open
#1,778 0 comments 0 reactions 0 assignees View on GitHub
:lady_beetle: bug
Dominant language
JavaScript
Stars
90
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Originally reported via e-mail:

> node recently (version 23) caused the inclusion of the
--no-experimental-fetch
command line parameter to be fatal. This parameter appears
in the following places and causes install to fall over:
install.sh
lively.classes/tools/build-runtime.sh
livelyprojects/templates/build-shell.js
. ../../scripts/lively-next-flatn-env.sh
local_projects/LivelyKernel-partsbin/tools/build.sh
scripts/check-boot.sh
lively-freezer/tools/build-loading-screen.sh
lively-freezer/tools/build-landing-page.sh

Contributor guide

Open the contributing guide

Research direction

Inspect the listed install and build scripts, starting with install.sh and scripts/check-boot.sh, and search them for --no-experimental-fetch. Verify the parameter is no longer passed in each listed location, then run the install flow with Node 23 to confirm it no longer fails.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.