Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom archive registry #424

Closed
guybedford opened this issue Jan 22, 2015 · 10 comments
Closed

Custom archive registry #424

guybedford opened this issue Jan 22, 2015 · 10 comments

Comments

@guybedford
Copy link
Member

An endpoint to support loading from tarball / zip URLs:

  jspm install archive:github.com/rase-/node-XMLHttpRequest/archive/a6b6f2.tar.gz

Where the assumption is that the protocol is https first, followed by http, with redirect following provided https -> https, falling back to http if not.

Does that make sense?

@subesokun
Copy link

For me this feature would make definitely sense in case it's allowed to install from local archives as well:

jspm install archive:/some/path/pkg-v1.0.0.tar.gz

I still have no solution ready to allow installing a complex package tree offline (e.g. by preparing a big package bundle and ship it as whole). But this archive endpoint would help at least to install all top-level dependencies.

@guybedford
Copy link
Member Author

Getting the addressing right is the hard part with this. Perhaps:

  jspm install http:github.com/file.zip
  jspm install local:c:\some\file.tar.gz

?

@subesokun
Copy link

That would be also ok for me. In case we don't have any space between local: and the file path the console auto completion won't work. In that case we can maybe also fall back to some OS agnostic filepath scheme? E.g.

jspm install archive:file://some/path/pkg-v1.0.0.tar.gz

But not sure if that is more confusing than helping.

@guybedford
Copy link
Member Author

  jspm install file:/some/path/pkg-v1.0.0.tar.gz
  jspm install http:github.com/file.zip

?

@subesokun
Copy link

yes that would make sense too me :) Just wondering if we should also support installing from folders in case the packages aren't packed e.g. developer just cloned some public repo but didn't create yet an archive out of it.

@guybedford
Copy link
Member Author

Yes it could support that as well for the file case, but not http. We could also potentially support installing a single js file too.

@guybedford
Copy link
Member Author

What is the version assumption for these endpoints? That's the biggest blocker for me here, and why I prefer to think of endpoints as "managed registries" with versioning included.

@guybedford
Copy link
Member Author

It is still a necessary feature - perhaps we can enable non-versioned endpoints in jspm.

@guybedford guybedford reopened this Mar 23, 2015
@bfil
Copy link

bfil commented Mar 25, 2015

+1 npm supports it, bower supports it, jspm should too :)

@guybedford guybedford changed the title Custom archive endpoint Custom archive registry Mar 25, 2015
@guybedford guybedford reopened this Apr 19, 2015
@guybedford
Copy link
Member Author

Looking to rather handle this via the new linking workflow at #622.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants