Install Atom Packages from Git URLs #355
Comments
Remember to do |
Thanks, good point. Will add to our documentation. That doens't solve the issue of course. This is the error I get:
|
He means:
Anyway, this is something that we'd like to have. The core team doesn't currently have it on the roadmap, but pull requests are welcome. |
@thedaniel Yup. I understood that part. Thanks for answer too. Good to know people are open to it. |
If apm packages are just GitHub repos, why not support: apm install username/repo
apm install username/repo/branch
apm install apm-package |
It'd be nice if worked with the exact same behavior as npm, which means supporting any remote git server, thus allowing the private development of plugins/modules before launch or even as a way to distribute private plugins (useful for internal tools that haven't been cleared for public use yet or never will) |
This comment has been minimized.
This comment has been minimized.
Would be really nice as I'm currently facing the exact same issue. |
+1 for this. I am trying to install a package that is falling and this would be helpful. |
+1 for this. I am trying to use a plugin that author has fixed the issues in the repo but not yet published the package update for the 1.0 atom api changes. |
#355 (comment) would be great! |
Problem arised from unable to specify dependencies with Git URLs (see atom/apm#355)
Fixed by #518 |
Hi,
Am I missing something or can you not install atom packages from git repos?
We're developing an atom package that we don't want to go live with. We're currently requiring people to do the following:
Run the following
Get them to run in development mode for it to work.
If it's not supported. We believe it should be for easier pre-release internal testing. We're building something cool but for marketing requirement reasons can't be developing pre-alpha in public.
Considerations appreciated,
Francois
The text was updated successfully, but these errors were encountered: