aleclarson/get-dev-paths

Search node_modules for locally developed packages

get-dev-paths

Search node_modules for symlinks that resolve to a package outside any node_modules directories.

Returns an array of symlink paths that match the following criteria:

• they live in node_modules
• their real paths are not in node_modules
• they exist in package.json (but not devDependencies)

Every matched package also has its node_modules searched.

Scoped packages are supported.

New in v0.1.1: Up to 50x faster!

import getDevPaths from 'get-dev-paths';

// When called with one argument, an array is returned which contains symlink
// paths that match the required criteria.
let paths = getDevPaths(process.cwd());

// When you want an array of resolved symlinks, set `preserveLinks` to false:
paths = getDevPaths(__dirname, {
  preserveLinks: false,
});

// When the returned array is missing an expected package, you can use the
// `onError` option to inspect why a symlink was skipped.
paths = getDevPaths(__dirname, {
  onError: console.error,
});

get-dev-paths's Issues

Symlinks seems stopped after update node.

const fs = require('fs')
const getDevPaths = require('get-dev-paths')

const projectRoot = __dirname
module.exports = {
  // Old way
  getProjectRoots: () => Array.from(new Set(
    getDevPaths(projectRoot).map($ => fs.realpathSync($))
  )),
  // New way
  watchFolders: Array.from(new Set(
    getDevPaths(projectRoot).map($ => fs.realpathSync($))
  ))
}

node: 11.3.0
metro: 0.50.0

not working, unless add the dependency which you linked in your package.json manually

I am working on a React-Native project, and I need test a package locally, before I publish it. So I need use yarn link

But yarn link does not work well with React-Native, because motro bundler does not support yarn link or npm link.

But I found metro-symlinked-deps, which will work according to its introduction.

So I tried it, but it not work well.

Then I check the metro-symlinked-deps source code, I found out it used this lib to get the linking package's path.

After some dig out, I found the local linking package path will not output unless it's name is in the project package.json

          fs.readdirSync(path.join(depsDir, name)).forEach(function(name) {
            if (deps[name = scope + '/' + name]) {
              return addPath(path.join(depsDir, name));
            }
          });

But seems like yarn link or npm link won't add the linking package name in the package.json

Currently, I add my local package's name in package.json manually. Like this:

"dependencies": {
    "myPackageName" : "*"
},

And it worked ~

I'm not sure whether I'm doing right or not, and the doc does not mention this.

So, could you help me to solve this problem?

Thanks a lot!