Bundle private / scoped dependencies with slc build --npm about strong-build

[sam-github]

Can you make npm pack bundle your deps? If not, its an npm bug, or a scoped package misfeature. Do you have an example I could run?

[sam-github]

Or can I at least have a copy of your package.json?

[barwin]

Hi @sam-github

Sure, here is a copy of my package.json:

{
  "name": "@ylopo/geocoder",
  "version": "0.2.0",
  "description": "Testing scoped dependencies.",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "node ."
  },
  "author": "Some Guy",
  "license": "None",
  "dependencies": {
    "@ylopo/service-logger": "^1.3.0",
    "MD5": "^1.2.1"
  },
  "devDependencies": {
    "grunt": "^0.4.5",
    "grunt-contrib-jshint": "^0.10.0"
  },
  "bundleDependencies": [
    "@ylopo/service-logger",
    "MD5"
  ]
}

After an slc build -b -p, the resulting .tgz file does have MD5 bundled, but it does not have the @ylopo/service-logger module.

Edit: I could not make npm pack bundle my deps .. so it sounds like it's an issue with npm. I still would appreciate a sanity check that my package.json looks like it should work before I take it up with npm.

Thanks for taking a look at this,

-Ben

[sam-github]

We call npm pack... so my opinion isn't worth much!

That said, you look like you are following the rules, your top-level package is scoped, and your deps are scoped.

[cgole]

@sam-github, does this need to be open? Any action required from our side.

[sam-github]

We could rewrite packing to not rely on npm, but other than that, we are blocked on npm fixing npm/npm#8614, this is a known bug.