Building NodeJS app snap and needed build folder is missing in staging step

snapcraft
1

I am trying to use snap for the first time to package a NodeJS app. Everything seems pretty simple except that symlinks are broken in the stage and prime step because a build folder is not copied during from the parts folder.

name: chuck
version: test
summary: Command line weather tool.
confinement: devmode
description: foobar

parts:
  command:
    plugin: nodejs
    node-engine: 8.12.0
    source: .
    build-packages:
    - python
    - build-essential

apps:
  chuck:
    command: bin/chuck

root@7241861fba6e:/tmp/app# tree -L 3 parts
parts
└── command
    ├── build
    │   ├── LICENSE
    │   ├── README.md
    │   ├── app.js
    │   ├── ci_scripts
    │   ├── config
    │   ├── dist
    │   ├── gulpfile.js
    │   ├── lib
    │   ├── node_modules
    │   ├── package-lock.json
    │   ├── package.json
    │   ├── scripts
    │   ├── test
    │   └── tsconfig.json
    ├── install
    │   ├── CHANGELOG.md
    │   ├── LICENSE
    │   ├── README.md
    │   ├── bin
    │   ├── include
    │   ├── lib
    │   └── share
    ├── npm
    │   └── node-v8.12.0-linux-x64.tar.gz
    ├── src
    │   ├── LICENSE
    │   ├── README.md
    │   ├── app.js
    │   ├── ci_scripts
    │   ├── config
    │   ├── dist
    │   ├── gulpfile.js
    │   ├── lib
    │   ├── node_modules
    │   ├── package-lock.json
    │   ├── package.json
    │   ├── scripts
    │   ├── test
    │   └── tsconfig.json
    └── state
        ├── build
        ├── prime
        ├── pull
        └── stage

root@7241861fba6e:/tmp/app# tree -L 3 stage
stage
├── CHANGELOG.md
├── LICENSE
├── README.md
├── bin
│   ├── mfp_executive -> ../lib/node_modules/@sixriver/mfp_executive/dist/lib/app.js
│   ├── node
│   ├── npm -> ../lib/node_modules/npm/bin/npm-cli.js
│   └── npx -> ../lib/node_modules/npm/bin/npx-cli.js
├── include
│   └── node
│       ├── android-ifaddrs.h
│       ├── common.gypi
│       ├── config.gypi
│       ├── libplatform
│       ├── node.h
│       ├── node_api.h
│       ├── node_api_types.h
│       ├── node_buffer.h
│       ├── node_object_wrap.h
│       ├── node_version.h
│       ├── openssl
│       ├── pthread-barrier.h
│       ├── stdint-msvc2008.h
│       ├── tree.h
│       ├── uv-aix.h
│       ├── uv-bsd.h
│       ├── uv-darwin.h
│       ├── uv-errno.h
│       ├── uv-linux.h
│       ├── uv-os390.h
│       ├── uv-posix.h
│       ├── uv-sunos.h
│       ├── uv-threadpool.h
│       ├── uv-unix.h
│       ├── uv-version.h
│       ├── uv-win.h
│       ├── uv.h
│       ├── v8-debug.h
│       ├── v8-inspector-protocol.h
│       ├── v8-inspector.h
│       ├── v8-platform.h
│       ├── v8-profiler.h
│       ├── v8-testing.h
│       ├── v8-util.h
│       ├── v8-value-serializer-version.h
│       ├── v8-version-string.h
│       ├── v8-version.h
│       ├── v8.h
│       ├── v8config.h
│       ├── zconf.h
│       └── zlib.h
├── lib
│   └── node_modules
│       ├── @sixriver
│       └── npm
└── share
    ├── doc
    │   └── node
    ├── man
    │   └── man1
    └── systemtap
        └── tapset

So my question is what am I doing wrong… it seems to expect that the build directory would be there, but its unclear why in my simple case it is not when it has what seems to be all the important information.

Is this possibly a bug in the nodejs snapcraft plugin? Or does it have something to do with my setup specfifically?

2

Managed to answer my own question…

using NPM just doesn’t seem to work, when I changed to using yarn for snap, it created without an issue.

1 Like
3

I had a similar problem (NPM not working, forced to use yarn)