Closed thesebas closed 8 years ago
Will fix it soon. Thanks
@h2non any update on this? I tried updating archiver to "^1.0.0" and this error disappears but I see this error running the test suite:
1) CLI get "before all" hook:
TypeError: Path must be a string. Received null
at assertPath (path.js:7:11)
at Object.dirname (path.js:1324:5)
at Object.getArgs (/Users/aledbf/github/nar/node_modules/stubby/src/console/cli.js:141:38)
at setupStartOptions (/Users/aledbf/github/nar/node_modules/stubby/src/main.js:60:18)
at Stubby.start (/Users/aledbf/github/nar/node_modules/stubby/src/main.js:92:12)
at module.exports.server (/Users/aledbf/github/nar/test/lib/helper.js:94:12)
at Context.<anonymous> (/Users/aledbf/gimake: *** [mocha] Error 8
I'll work on this sometime during the weekend. Sorry for the delay.
@h2non don't push yourself. it's not like we're paying you. thanks for this excellent package!
Fixed in nar@0.3.37
. Feel free to update to latest version: npm u -g nar
@h2non I see this error running extract, run or list: Error: The given path is not a file
$ nar -V
0.3.37
$ node -v
v6.1.0
Will try to reproduce the issue.
@aledbf cannot reproduce the issue. Just tried to create multiple nar
executable containers and then running or extracting them. No problems. I'm running the same versions as you are.
If you can share some package.json
as example or the commands you're running, that would be helpful to me.
@h2non I found the issue: the name of the package cannot be private (@myorg/demo
). Removing @myorg
solved the issue.
Then I can provide a solution for that case.
@h2non Any news on this? Can't really rename the package...
To reproduce you can use the linked PR
See: https://github.com/h2non/nar/issues/140 nar still do not support private package names (but it can procees private dependencies).
It should be simple to fix. I will try to fix it soon, or feel free to send a PR.
I'll provide a PR asap
when trying to create archive
nar create
got this errorseems that node >=5.6 has some changes with creating buffers and it seems to be fixed in recent versions of
archiverjs/node-archiver