Namespace issues between Atom and Node packages

[idleberg]

Prerequisites

• [x] Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Atom package can't share the name of a Node dependency. For instance, if my Atom package is called build and it depends on a Node package named build, then publishing the package will fail. In my opinion, it should always be encouraged to use simple names. While the number of conflicts might be manageable at this point, they will only increase with the continuing popularity of Node.

Steps to Reproduce

1. Create a package called bootstrap
2. Add bootstrap as a dependency
3. Try publishing the package

Expected behavior: Maybe apm should internally prefix Atom packages to avoid these conflicts (e.g. apm.author.package) . In any case the error message could be more explicit about the actual problem.

Actual behavior: Publishing fails

Reproduces how often: 100%

Versions

apm  1.18.4
npm  3.10.10
node 6.9.5 x64
python 2.7.13
git 2.11.0

(I remember having run into this issue several versions ago!)