node app builds forked, but not referencing upstream source
Metadata
Current evaluation
Snapcraft 2.34 node plugin fails to build when source is a remote URL (rimraf not found, node_modules missing) while a local checkout builds fine. 8.8 years old, zero maintainer interaction; the 2.x node plugin has since been rewritten in snapcraft 8.x.
Suggested action: close stale
Reason: The reporter targets snapcraft 2.34 from candidate (2017), and the issue has had zero comments or maintainer interaction for 3218 days. The 2.x node plugin no longer exists in the current codebase (snapcraft 8.x has a rewritten parts system under snapcraft/parts/), so the affected version is no longer supported and the original problem is not reproducible on a current release. Closing as stale is appropriate rather than triaging, since no current-version relevance can be established.
Impact:
15
Quick Win:
8.25
Staleness:
95
Complexity:
45
Confidence:
75
Support Request:
10
Issue body
nba-go seems to build okay when forked, but not when you have a source line pointing to an external URL.
git clone https://github.com/elopio/nba-go.git
cd nba-go
git checkout snapcraft
snapcraft cleanbuild
^ this works
Now copy that url out to an empty dir and change the source line to be
source: https://github.com/xxhomey19/nba-go.git
Then "snapcraft cleanbuild". It fails to build.
I'm using snapcraft, version 2.34 from candidate.
yarn run v1.3.2
$ npm run clean && babel src -d lib --copy-files --ignore '**/*.spec.js' -s
> nba-go@0.1.9 clean /root/build_nba-go/parts/nba-go/src
> rimraf lib
sh: 1: rimraf: not found
npm ERR! Linux 4.10.0-38-generic
npm ERR! argv "/root/build_nba-go/parts/nba-go/install/bin/node" "/root/build_nba-go/parts/nba-go/install/bin/npm" "run" "clean"
npm ERR! node v6.10.2
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! nba-go@0.1.9 clean: `rimraf lib`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the nba-go@0.1.9 clean script 'rimraf lib'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nba-go package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! rimraf lib
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nba-go
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nba-go
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /root/build_nba-go/parts/nba-go/src/npm-debug.log
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
8.25
Staleness:
95
Complexity:
45
Confidence:
75
Support Request:
10
|
close stale | Snapcraft 2.34 node plugin fails to build when source is a remote URL (rimraf not found, node_modules missing) while a local checkout builds fine. 8.8 years old, zero maintainer interaction; the 2.x node plugin has since been rewritten in snapcraft 8.x. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
90
Support Request:
30
|
close stale | Snapcraft node plugin fails to build when source points to an external URL, citing missing node_modules and rimraf. Issue is over 8 years old with zero maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
85
|
close stale | Snapcraft build fails when using an external source URL due to missing node_modules and rimraf dependency. Issue is 8+ years old, references deprecated Snapcraft 2.34, and has no maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
30
Confidence:
90
Support Request:
45
|
close stale | Snapcraft build fails when using external URL source instead of a forked repo, citing missing node_modules/rimraf. Issue is over 8 years old and references snapcraft 2.34. | |
| qwen3.6-35b-moe-q4 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
20
|
close stale | Snapcraft cleanbuild fails with missing node_modules when using an external git source URL. The issue is over 8 years old, unlabelled, and lacks maintainer engagement. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1819804 nodejs plugin: build fails if there are missing peer dependencies. | snapcraft (launchpad) | open | Snapcraft nodejs plugin build fails when npm ls --json exits non-zero on missing peer deps; the CalledProcessError fallback is dead code since run_output wraps it in SnapcraftPluginCommandError. Open 7.5 years, unlabelled, no maintainer activity. | |
| #1710256 nodejs snaps fail when source is not a local directory | snapcraft (launchpad) | closed | The nodejs plugin incorrectly constructs the package.json path when using a remote URL as source, breaking snap builds. The report was closed without a fix or resolution. |