What about adding possibility to change default installation folder from 'node_modules' to something else in 'napa-config':

"napa-config": {
"install-folder": "web_modules"
}

Why it could be useful?

For example webpack is set by default to search for modules in 'web_modules' and 'node_modules' directories. By installing all libraries available in npm to 'node_modules' and libraries that aren't published in npm to 'web_modules' we could use 'npm shrinkwrap' without any issues.

Not sure if this idea have some downsides but I think it could work well. What do you think?

I find this package in one page, when i search how to ues bowserify build angular project.
It use napa to install angualr module to node_modules. because angular module haven't been published in npm.
But without this usage, I can't know where to use it.
Npm also support install via git.

So, I want to know where this package used to .
In the other hand, Why I use napa instand of npm.
Or, What's purpose of this package.

I'm Chinese. English is my second language. if spelling error or syntax error occured, sorry.
Thanks.

napa doesn't seems to use the correct package name when using the following format:

{
  "scripts": {
    "install": "napa"
  },
  "napa": {
    "srcpubnub": "pubnub/javascript#3.7.2"
  }
}

napa create node_modules/srcpubnub/package.json with this content:

{
  "name": "pubnub",
  "version": "0.0.0",
  "description": "",
  "_napaResolved": "https://github.com/pubnub/javascript/archive/3.7.2.tar.gz"
}

While I believe the package name should be srcpubnub.

Else npm shrinkwrap will complain about it

❯ npm shrinkwrap
npm ERR! Error: Problems were encountered
npm ERR! Please correct and try again.
npm ERR! invalid: [email protected] /Users/nrako/project...name/node_modules/srcpubnub

Manually editing the package name, fix that. Of course srcpubnub has to be added to the optionalDependencies.

Am I correct? The package name should reflect the folder name/napa config, right?

Can you update the download module version and make the @3.2.0 in the available range ?

In actual version (@3.1.x), an old version of url-regex is used and it rejects this valid url : http://localhost:8081/nexus/content/sites/local-frontend-repository/github/angular-ui/bootstrap-bower-0.12.0.zip

The @3.2.0 uses the latest version of url-regex, and my url is now accepted.

Thx in advance.

It would be nice if napa could manage something like that

"napa" : {
  "foo" : "http://foobar/foo*.js",
  "bar":  "http://foobar/bar-(foo1,foo2).min.js"
}

to retrieve all matching foo*.js + bar-foo1.min.js and bar-foo2.min.js

I don't find any solution to download a private repo with napa.

I was trying to use napa to download atom-shell for Windows from their GitHub release page (https://github.com/atom/atom-shell/releases/download/v0.19.5/atom-shell-v0.19.5-win32-ia32.zip). It then proceeds to try to download it as a git repo since the URL contains "github.com" but does not contain "/archive/" (per the logic in pkg.js).

So for funzies, I added "?/archive/" to the end which did enable it to download and unzip the resource but then fell prey to #12 (DOHZ!). And so I am back to using the grunt (gulp!) atom-shell download plugin ... but using napa makes all my non-package.json-containing "modules" so much more consistent, unified, glorious, etc. :)

Of course, a fix to #12 could have been good enough but I thought I'd enter this issue for the sake of idealism ... or something.

So then, is there something obvious I am missing here? Maybe detecting GitHub repo URLs could be more specific (a la regex for example) or, at the very least, another exclusion could be made to check for "/releases/"? What do you guys think?

Cheers and good work friends

When I add more modules with napa, napa installs whatever I'm trying to add, but deletes whats in the directories the things I have previously installed with napa

For example
package.json:

{
  "scripts": {
    "install": "napa"
  },
  "napa": {
    "foo": "username/repo"
  }
}

then i run npm install and foo is installed under node_modules directory.

then i change package.json to

{
  "scripts": {
    "install": "napa"
  },
  "napa": {
    "foo": "username/foo",
    "bar": "username/bar"
  }
}

then run npm install, napa will install bar in the node_modules directory, but /node_modules/foo will be empty.

Am I doing something wrong?

some/package.git#specifier checks out master everytime.

For example, I'd like to use napa to download a binary: https://github.com/kreuzwerker/envplate/releases/download/v0.0.8/ep-linux

Is it possible to do this? If not, I think it would be a nice feature to be able to download single files with napa.

Hi !

When i use the # feature on the angular ui bootstrap repo (https://github.com/angular-ui/bootstrap), the directory structure is flat : all files from the project are in the root directory.

i'm on windows

{
  "devDependencies": {
    "napa": "~0.4.1"
  },
  "scripts": {
    "install": "napa"
  },
  "napa": {
    "bootstrap": "twbs/bootstrap",
    "angular": "angular/bower-angular",
    "angular-ui-bootstrap": "angular-ui/bootstrap#v0.10.0"
  }
}

When running npm install I get the following:

0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'install' ]
2 info using [email protected]
3 info using [email protected]
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly rollbackFailedOptional Starting
8 silly rollbackFailedOptional Finishing
9 silly runTopLevelLifecycles Starting
10 silly runTopLevelLifecycles Finishing
11 silly install printInstalled
12 verbose stack Error: ENOENT, open '/home/ashton/workspace/big-realtime-app/node_modules/ceaser/package.json'
12 verbose stack     at Error (native)
13 verbose cwd /home/ashton/workspace/big-realtime-app
14 error Linux 3.13.0-29-generic
15 error argv "node" "/usr/local/bin/npm" "install"
16 error node v0.12.4
17 error npm  v3.0.0
18 error path /home/ashton/workspace/big-realtime-app/node_modules/ceaser/package.json
19 error code ENOENT
20 error errno -2
21 error enoent ENOENT, open '/home/ashton/workspace/big-realtime-app/node_modules/ceaser/package.json'
21 error enoent This is most likely not a problem with npm itself
21 error enoent and is related to npm not being able to find a file.
22 verbose exit [ -2, true ]

Relevant part of package.json:

{
  "napa": {
    "ceaser": "git://github.com/matthewlein/Ceaser"
  }
}

Would be great if I cloud do:

{
 "napa": {
    "angular": "angular/bower-angular#v1.2.3",
    "ui-router": "angular-ui/ui-router#master",
    "angular-mocks": "angular/angular-mocks"
  }
}

When you run npm install install over a project with napa-installed packages, npm throws the following:

npm WARN package.json [email protected] No repository field.

The said repo: gdsmith/jquery.easing.

The spec doesn't seem to say anything about the repository field being required. But it's not nice to see npm shouting at me.

I get an error from napa when running npm install, but it seems to work fine.

Here are the legit bits of my package.json

{
  "version": "0.1.0",
  "main": "index.js",
  "private": "true",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "install": "napa"
  },
  "dependencies": {
    "express": "~3.2.6",
    "connect": "~2.12.0"
  },
  "devDependencies": {
  ...
    "napa": "~0.4.0"
  },
  "napa": {
    "angular": "angular/bower-angular",
    "ui-router": "angular-ui/ui-router"
  },
}

When I run npm install I get this

localhost:eqfront shane$ npm install

> [email protected] install /Users/shane/Sites/eqfront
> napa

info install git://github.com/angular/bower-angular into node_modules/angular
info install git://github.com/angular-ui/ui-router into node_modules/ui-router
ERR! Cloning into '/Users/shane/Sites/eqfront/node_modules/angular'...

ERR! Cloning into '/Users/shane/Sites/eqfront/node_modules/ui-router'...

But as I said, it clones those two packages just fine into node_modules

Any ideas?

I getting this error on project and don't know why.

info download https://github.com/twbs/bootstrap/archive/v3.3.2.tar.gz into bootstrap
info cache https://github.com/FortAwesome/Font-Awesome/archive/v4.2.0.tar.gz into FontAwesome
info cache https://github.com/madebysource/lesshat/archive/v3.0.2.tar.gz into lesshat
info cache https://github.com/daneden/animate.css/archive/v3.1.0.tar.gz into animate.css
info cache https://github.com/scottjehl/picturefill/archive/2.2.0.tar.gz into picturefill
info cache https://github.com/ded/script.js/archive/v2.5.7.tar.gz into script
info cache git://github.com/kenwheeler/slick into slick
info cache git://github.com/lokesh/lightbox2 into lightbox2

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: EISDIR, read

this is what i have in package.json

  "napa": {
    "bootstrap": "twbs/bootstrap#v3.3.2",
    "FontAwesome": "FortAwesome/Font-Awesome#v4.2.0",
    "lesshat": "madebysource/lesshat#v3.0.2",
    "animate.css": "daneden/animate.css#v3.1.0",
    "picturefill": "scottjehl/picturefill#2.2.0",
    "script": "ded/script.js#v2.5.7",
    "requestAnimationFrame": "darius/requestAnimationFrame",
    "angularUtils": "michaelbromley/angularUtils",
    "slick": "kenwheeler/slick",
    "xhr": "LuvDaSun/xhr-polyfill",
    "lightbox2": "lokesh/lightbox2"
  },

How can napa support peer dependencies?

Possible fix:

f12552f

I want to install a specific version of a bower package, e.g. angular-strap#2.0.0-rc.4.

How can I specify that to napa please?

Is there a way to prevent napa from reinstalling packages every time it runs?

Let's assume my package.json looks like this:

"dependencies": {
    "express": "3.x"
},
"napa":{
  "angular":"http://some.com/path/to/angular.git"
}

• If I run npm install once, it will download and install express. If I run npm install a second time, it will recognize that express 3.x is installed and not reinstall it
• If I run napa once, it will download and install angular. If I tun napa a second time, it will download and install angular again. And again. And again.

Is there any way that we can have napa recognize that it has already installed this fileset and not reinstall it? Understandably, npm install has a versionizing system, which npm relies upon to determine what is installed and what is not, while napa has no central repo to hit and check published version numbers. Is there any alternate way of doing it here?

npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/bin/iojs" "/Users/casey/.npm/bin/npm" "install"
npm ERR! node v4.1.0
npm ERR! npm  v3.2.1
npm ERR! path /Users/casey/Code/UniversitySite/node_modules/flippant
npm ERR! code EISGIT

npm ERR! git Appears to be a git repo or submodule.
npm ERR! git     /Users/casey/Code/UniversitySite/node_modules/flippant
npm ERR! git Refusing to remove it. Update manually,
npm ERR! git or move it out of the way first.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/casey/Code/UniversitySite/npm-debug.log

and relevant package.json section

"napa": {
  "flippant": "mintchaos/flippant.js",
}

Would it be possible to add a flag that forces napa to not use the internal cache?

I'm pretty sure it should be installed as a devDependencies, but a small note in the README would be great. Hum... Waiting for you input, then maybe I'll send a PR to change the install command to npm install --save-dev napa

When you change a npm dependency's reference in package.json, it automatically gets uninstalled, and the new version gets downloaded and installed.

In napa you have to uninstall manually, take care of the cache (see my pull request), then reinstall. It would be über-cool if updating a napa dependency worked as seamlessly as updating an npm dependency.

If napa detects that the downloaded files don't contain a package.json, it currently creates one. I would add that it should be smart about the main attribute.
If there is a file on the root with the same name of the package, use that as main. For example, if I specify that I want to use jquery-validation-unobtrusive, and that the name I want to use for it is jquery.validate.unobtrusive, it should set the main to jquery.validate.unobtrusive.js, which is a file of the same name that is located on the root.
Maybe also check /lib and /bin.
This is somewhat connected to what was proposed on #18, but it would offer a convention, so I don't always need to configure.

Say the only way a package was released was via a single prepackaged URL say a CDN. It would be great to be able to specify:

{"example": "https://example.com/cdn/foo"}

Downloads foo and moves it into node_modules/example/index.js

Would it make sense to add a --save flag to napa?
So when you run napa username/repo --save it will add the repo to "napa" in package.json.

askovpen/node-fidonet-mailer-binkp-crypt#1

Do you know if you can use something else?

When you do npm prune, it removes packages installed by napa. It's a nonsense as it's defined in napa key in package.json.

It sounds logical though about npm but a fix should be done.

What do you think?

path.js:8
    throw new TypeError('Path must be a string. Received ' +
    ^

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:8:11)
    at Object.posix.join (path.js:477:5)
    at new NapaPkg (/Users/casey/Code/napa/lib/pkg.js:23:25)
    at /Users/casey/Code/napa/cli.js:22:15
    at Array.forEach (native)
    at Object.napa.cli (/Users/casey/Code/napa/cli.js:19:8)
    at Object.<anonymous> (/Users/casey/Code/napa/bin/napa:3:22)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)

Attributed to some variables missing var

I am using napa.cli() in my npm install script as a module. It's working great, but the callback (second arg) is never called.
I think it's because the condition (total < 1) in cli.js l.11 is never met. Lines 11 and 12 should be swapped.

Would be much easier to keep things in order, and it would ensure that napa is installed before being run.

@shama

Seems like this is related to new git 1.8.5.2 & 1.9.0.

Upgraded my git to 1.8.5.2 or/ 1.9.0 caused napa to start erroring. Everything 'seems' fine with the clone though.

Reverting back to 1.8.3.4 fixes it.

My package.json

....

  "napa": {                                                                    
    "angular": "angular/bower-angular",                                        
    "angular-route": "angular/bower-angular-route"                             
  }, 
  ...etc.              

Assuming this config :

"scripts": {
    "install": "napa "
},
"napa": {
    "angular-bootstrap": "http://github.com/angular-ui/bootstrap-bower/archive/0.12.0.zip",
    "angular-bootstrap2": "http://napa.farmercorp.com/github/0.12.0.zip"
}

Both archives are the extact same file. But, only the github archive will be downloaded to node_modules/. The other one seems to be ignored.

See the verbose log :

...                                             
> napa                                                                                                                                                   

info download http://github.com/angular-ui/bootstrap-bower/archive/0.12.0.zip into angular-bootstrap                                                       
info download http://napa.farmercorp.com/github/0.12.0.zip into angular-bootstrap2                                                                         

... 
...                                                                                                                                          ```

I have declared in my package.json:

"napa": {
  "jquery": "jquery/jquery#v2.1.4"
}

I run "napa" in the terminal and it says:

info download https://github.com/jquery/jquery/archive/v2.1.4.tar.gz into jquery

Then it ends the command, but no jquery folder appears in my node_modules.
Any clues?

Is there any chance that there will be added subversion support any time soon?

I used napa to install a library, but had a trouble of missing files.
It turned out that files are gone with cache install.
Deeper investigation revealed that the pack procedure ignores .gitignore files.
Although this might be a desired behavior, it was a fatal issue for me.
I have created a modified version for now,

7ceed6a

but it might be good to have such a feature, possibly optionally.

Please add support for installing git repos over https protocol. It's the only way to install closure-library I found. The url looks like git+https://code.google.com/p/closure-library/#740af00c1f9ee58544ba556d0a4fc2c13c16761a.

Since napa is meant to be used with libraries that don't supply package.json, it could be useful to allow the user to specify their own custom file to integrate more naturally with node.js.

My use case is simple: I don't want to have to require the absolute path to the "index" file of a library.

In other words, this is what I'm doing now:

var lib = require('lib/bin/index.js');

...when I'd much rather just be able to do this:

var lib = require('lib');

So my suggestion is to allow the user to specify a package.json body along with any URL.

Example:

package.json:

{
  ...
  "napa": {
    "lib": {
      "url": "user/lib",
      "package.json": {
        "main": "bin/index.js"
      }
    }
  }
}

Another use-case might be a package that needs to be built ahead-of-time:

package.json:

{
  ...
  "napa": {
    "lib": {
      "url": "user/lib",
      "package.json": {
        "main": "bin/index.js",
        "scripts": {
          "install": "make"
        }
      }
    }
  }
}

I realize all of this could technically be achieved through scripts, but this would offer a more localized configuration.

Thoughts?

I have a two projects, A and B for brevity.

project A uses napa to install dependencies from github

project B installs project A as a dependency

the install fails if project B does not have napa installed as well, which means that project B needs to "know" about project A's dependency on napa in order to use it.

Is there a way to resolve this?

If this is even possible, hopefully it is.

I'm thinking something like:

  "napa": {
    "example-library-from-url": {
        "url": "https://example.com/path/to/library.js?with-options=in-query",
        "location": "index.js"
    }
  }

Downloading from a github repo, try to make a typo in the reference – everything will pass smooth and error-less, yet the package isn't installed.

It would be great to:

• see a warning if something goes wrong, and
• see a summary at the end when things go right.

Hello @shama

First of all thank you for your package!

I'm trying to switch to https://yarnpkg.com/ from npm currently. ANd just curious is there a way to use napa package with yarn?

I was downloading a a zip file, but the first level of folders inside the zip was always stripped, breaking the folder structure completely. Similar to #12
I was trying to fiddle around with the strip option, but no difference.

I used the download package directly and it failed, too. But after installing the current version 5 of download my script worked and the zip was extracted correctly. So, maybe if you update this dependency these errors resolve.

The zip file: http://kangoextensions.com/kango/kango-framework-latest.zip

When I try to install a zip or tar.gz I get this error:

info download https://github.com/openseadragon/openseadragon/releases/download/v2.0.0/openseadragon-bin-2.0.0.zip into openseadragon
info git https://github.com/fabiobiondi/angular-fullscreen into angular-fullscreen
info git https://github.com/lodash/lodash.git into lodash-frontend

/home/www/pic-pixel/node_modules/napa/node_modules/download/node_modules/each-async/node_modules/onetime/index.js:15
throw new Error(fnName + ' can only be called once.');
^
Error: callback() can only be called once.
at DuplexWrapper.<anonymous> (/home/www/pic-pixel/node_modules/napa/node_modules/download/node_modules/each-async/node_modules/onetime/index.js:15:11)
at DuplexWrapper.EventEmitter.emit (events.js:95:17)
at readableAddChunk (/home/www/pic-pixel/node_modules/napa/node_modules/download/node_modules/readable-stream/lib/_stream_readable.js:178:12)
at DuplexWrapper.Readable.push (/home/www/pic-pixel/node_modules/napa/node_modules/download/node_modules/readable-stream/lib/_stream_readable.js:162:10)
at DestroyableTransform.<anonymous> (/home/www/pic-pixel/node_modules/napa/node_modules/download/node_modules/stream-combiner2/node_modules/duplexer2/index.js:50:15)
at DestroyableTransform.EventEmitter.emit (events.js:95:17)
at DestroyableTransform.<anonymous> (/home/www/pic-pixel/node_modules/napa/node_modules/download/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:786:14)
at DestroyableTransform.EventEmitter.emit (events.js:92:17)
at emitReadable_ (/home/www/pic-pixel/node_modules/napa/node_modules/download/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:448:10)
at emitReadable (/home/www/pic-pixel/node_modules/napa/node_modules/download/node_modules/vinyl-fs/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:444:5)