ARMmbed / ARMmbed/dapjs

fail to build

Open
#75 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
134
Forks
56
PR merge metrics
No merged PRs in 30d

Description

Hi,
You guys mentioned in readme.md that Gulp is used as a task runner to build the project. But I can't find gulpfile.js in this program. Besides, I failed to run `npm run build` to build this program. The logs are as follow:

`
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build'
1 verbose cli ]
2 info using npm@6.14.6
3 info using node@v12.18.3
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle dapjs@2.2.0~prebuild: dapjs@2.2.0
6 info lifecycle dapjs@2.2.0~build: dapjs@2.2.0
7 verbose lifecycle dapjs@2.2.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle dapjs@2.2.0~build: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\coding\dapjs\node_modules\.bin;C:\Users\tinker\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\tinker\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\Git\cmd;C:\WINDOWS\System32\OpenSSH;C:\Program Files\nodejs;C:\ProgramData\chocolatey\bin;C:\Python38;C:\Users\tinker\AppData\Local\Programs\Python\Python38\Scripts;C:\Users\tinker\AppData\Local\Programs\Python\Python38;C:\Users\tinker\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Bandizip;D:\Programs\Microsoft VS Code\bin;C:\Users\tinker\AppData\Roaming\npm;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle dapjs@2.2.0~build: CWD: D:\coding\dapjs
10 silly lifecycle dapjs@2.2.0~build: Args: [ '/d /s /c', 'rollup -c && typedoc src' ]
11 silly lifecycle dapjs@2.2.0~build: Returned: code: 1 signal: null
12 info lifecycle dapjs@2.2.0~build: Failed to exec build script
13 verbose stack Error: dapjs@2.2.0 build: `rollup -c && typedoc src`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid dapjs@2.2.0
15 verbose cwd D:\coding\dapjs
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v12.18.3
19 verbose npm v6.14.6
20 error code ELIFECYCLE
21 error errno 1
22 error dapjs@2.2.0 build: `rollup -c && typedoc src`
22 error Exit status 1
23 error Failed at the dapjs@2.2.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
`

Could anyone help me? Thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Compare the README.md claim about Gulp with the build command shown in the issue, which runs `rollup -c && typedoc src`; inspect the project's build configuration and reproduce `npm run build` using the reported Node and npm versions. Done means the documented build process matches the repository and the command completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, rollup, typescript
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.