← Back to issue list

Can not use NodeJS 8

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1755524
Type
issue
State
open
Author
~ark9719
Labels
—
Created
Updated
Closed
—

Current evaluation

snapcraft nodejs plugin build failures when pinning node-engine to 8.10.0 (missing bin, Text file busy on node). No comments or labels; closed without a fix. NodeJS 8 is long EOL and the plugin has since been rewritten.

Suggested action: close stale

Reason: The issue is already closed with zero comments and no fix, and it targets NodeJS 8, which has been EOL since December 2019. The related Launchpad bug 1703643 ('node-engine: 8.1.3 is not happy') was likewise closed as stale because the nodejs/npm plugin has changed considerably since the report, so the original problem no longer applies to current snapcraft.

Impact: 5 Quick Win: 2.75 Staleness: 95 Complexity: 45 Confidence: 80 Support Request: 10

Issue body

#### Issue description When declaring a node version 8.X.X, snapcraft builds fail with a variety of errors. #### Steps to reproduce the issue 1. Explicitly point 'node-engine' to 8.10.0 2. run 'snapcraft' ``` name: hello-node-snap version: "1.0.2" summary: A simple hello world command description: hello world confinement: strict apps: hello-node-snap: command: bin/hello-node-snap plugs: [network] parts: hello-node-snap: plugin: nodejs node-engine: 8.10.0 node-packages: - hello-node-snap ``` #### What's the expected result? I've received the following errors: [Errno 2] No such file or directory: mysnapdirectory/prime/bin/hello-node-snap OSError: [Errno 26] Text file busy: mysnapdirectory/parts/hello-node-snap/install/bin/node #### Additional details It looks as if npm is creating a package.json lockfile and silently failing.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 5
Quick Win: 2.75
Staleness: 95
Complexity: 45
Confidence: 80
Support Request: 10
close stale snapcraft nodejs plugin build failures when pinning node-engine to 8.10.0 (missing bin, Text file busy on node). No comments or labels; closed without a fix. NodeJS 8 is long EOL and the plugin has since been rewritten.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 15
close stale Snapcraft build fails when targeting Node.js 8.10.0 due to missing binaries and file busy errors. Issue is completely inactive after 8 years with no maintainer response or labels.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 35
Confidence: 90
Support Request: 10
close stale Snapcraft build fails with Node.js 8.10.0 due to file busy and missing binary errors. Unlabelled, zero comments, and inactive for over 8 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 10
Confidence: 95
Support Request: 20
close stale Snapcraft builds fail with Node.js 8.10.0 due to missing binaries and file busy errors. Unaddressed for over 8 years with no maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 20
close stale Snapcraft builds fail when targeting Node.js 8.x due to npm lockfile generation and file locking errors. The report remains open, untriaged, and inactive with no comments.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft (launchpad)#1703643 (confidence 70%)

    Same node-engine plugin area (8.1.3 cleanbuild failure); closed as stale because the npm plugin changed considerably since the report.

Related issues

Issue Project State Summary Similarity
#2001 node-engine does not support NodeJS 8.X.X snapcraft closed Closed without resolution or fix due to inactivity. The report detailed snapcraft build failures with Node.js 8.x caused by npm lockfile creation and file locking errors, but received no comments or patches.
80%
#1703643 node-engine: 8.1.3 is not happy snapcraft (launchpad) closed Closed as stale. The node-engine 8.1.3 cleanbuild failure stemmed from a missing staging directory. The npm plugin has changed considerably since the report, so the issue was abandoned without a direct fix.
72%