New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tarball packed by slc build -ibp --scripts does not include the build/ subdirectory #10
Comments
I'm assuming the command was actually The binary parts of node-syslog are blocked from packing by node-syslog's own .npmignore file. Something else to note is that statsd installed this way has a non-empty .npmignore file as generated from the .gitignore file in the repo it was published from. |
there .npmignore file is meaningless, it only ignores node_modules, which is always ignored, but the bundledependencies was correctly updated. not sure what's going wrong. and yes, I typed the command wrong |
I think |
Yes, it does not pack build/ directories... we can't use it. Argh! Unless that behaviour is configurable. |
It worked as expected when I deleted |
Ah, I was reading too fast... it's node-syslog's .npmignore that is the problem, and yes, you are right. This is going to be a problem for us. Anybody who uses a .gitignore will have build in it, and that is OK. But anybody who writes a .npmignore is going to also have build/ in it... and that is going to make it impossible to pack binary dependencies. We'll need a fix. |
@rmg, I think we have to write out own tarball (not use Do you agree? You've used the npm tgz implementation, I think, any estimate on time to do that? |
For the purposes of building a bundled tarball, what about just removing any .gitignore and .npmignore files found under |
That sounds like a better idea than mine. |
Published to staging: |
I did
And the packfile produced did not include node_modules/node-syslog/build/....
The text was updated successfully, but these errors were encountered: