Open mnquintana opened 9 years ago
Yeah, this is expected, apm
is not a package published to atom.io, it is a library published to npmjs.org
We could special-case this though to make it easier to hack on apm.
Ah okay, I had a feeling it was something like that.
I think making it a special case seems like a good idea - if it turns out that isn't the best route, I think the best compromise would be to display a warning and help text for the preferred way to hack on apm.
:+1:
apm develop apm
returnsRequest for package information failed: Not Found
apm develop <any-other-core-package>
works normally