coolaj86/node-pakman

An API for building higher-level node package managers (such as Ender)

Moved

node-pakman is now at git.daplie.com/coolaj86/node-pakman

node-pakman's Issues

multiple local requires only renames first `require` in pakmanaged.js

A new test case, garply, has been added

./lib/four
./lib/four/index.js
./lib/one.js
./lib/two
./lib/two/three.js
./lib/two.js
./main.js
./package.json

main.js:

require('./lib/one');
require('./lib/four');
require('./lib/two/three');
require('garply/two');

All of the provides are correct, but only one of the ./lib/xyz-style requires is renamed correctly.

require('/tmp/foo') should detect as local module and warn

This shows a warning, as expected:

require('../../../../../../tmp/foo')

This does not:

require('/tmp/foo')

Really, requiring anything outside of package.json.lib should warn.

superfluous "never require'd" warning for aliased packages

Problem:

[WARN] The following packages are listed in package.json, but never `require`d:
  events.node

Solution:

If the package.json lists an alias, then use the alias for checking instead

"dependencies": [] -- array fail!

When package.json.dependencies is an array rather than an object, it isn't handled properly.

Test case: build with underscore

superfluous "never require'd" warning for ender packages

Problem:

[WARN] The following packages are listed in package.json, but never `require`d:
  qwery
  bean
  bonzo
  domready

Possible Solution:

All dependencies which have an ender.js bridge file should be considered as used, even when not required.

issue#1 needs test case

issue #1 needs test case

respect version numbers (package.json.browserDependencies)

Currently no version numbers are respected.

Obviously we can't address version hell the same way in the browser as on a file system (having 100 copies of the same module all over the place), but we can use the same workaround (just install the working version in the root package).

`package.json.browser` should supersede `package.json.main`

There should be a way to pass in which key should be treated as main as well as which key should be treated as dependencies.

Gets confused with files of same name in different directories

I was trying to get node-coordinator to work with pakmanager, and it seems that pakmanager gets confused. Here's the directory structure

• coordinator.js
• lib
  • utm.js
  • latlong.js
  • mgrs.js
  • usng.js
  • utm
    • helpers.js
  • latlong
    • helpers.js
  • mgrs
  • usng

Both helpers.js get converted to 'examples/.lib/utm/helpers'. While my directory structure is a little unusual, I can see other repos having files with the same name on the same level. When I renamed one, it worked.

I'll see if I can pare this down a little.