Xianming Zhong

Thanks for your share. And what's your opinion on [webpack's own alias](https://webpack.js.org/configuration/resolve/#resolvealias)?

Do you agree with the discussion in #346, as well as webpack's own alias config is good enough, or maybe better, to handle module resolution?

You project structure is a little hard to be understood. Can you draw a better tree graph?

I guess you installed a package without its peerDependencies. Make sure babel compiles all your files, even if they are in node_modules.

It works as expected. Regular expressions do nothing for double asterisks. You can try [passing-a-substitute-function](https://github.com/tleunen/babel-plugin-module-resolver/blob/master/DOCS.md#passing-a-substitute-function), i.e. writing some logics to check files existents. And I suggest you make your alias...

In theory, it can be achieved by [conditional types](https://www.typescriptlang.org/docs/handbook/advanced-types.html#conditional-types). See examples like https://github.com/sindresorhus/pify/pull/76. @szmarczak If you agree with this kind of mechanism, I can send a PR to handle `options.resolveBodyOnly`....

@sindresorhus Would you mind setting up coverage report? Like codecov.io or coveralls.

@esamattis It works for me. Where did you put the `.np-config.json` file in? Don't place it in your source subfolder. It should be in the project root. If possible, you...

@sindresorhus Checked and commented some issues today. If I can add labels for issues, that would be greater. Glad to help anyway.

This is due to your repository has 2 initial commits, which results in our `firstCommit` function in `git-utils.js` doesn't work as expected. After a tag was created, it will not...