error on jspm install about skeleton-navigation

[EisenbergEffect]

The answer and the solution are right in front of you 😄

GitHub rate limit reached. To increase the limit use GitHub authentication.
Run jspm endpoint config github to set this up.

Also, there is a note about this in the documentation which explains it.

[sgruhier]

Thanks!
This is Friday night, sorry for that stupid issue

[EisenbergEffect]

No need to apologize. This is not really ideal. I'm trying to talk to the jspm team to see if there's some way to improve this for the future. You aren't the first one to get caught.

[sgruhier]

I had to run a bunch of npm install to be able to run gulp watch

 npm install require-dir
 npm install orchestrator
 npm install gulp-util
 npm install deprecated
 npm install vinyl-fs

May be I did one more thing wrong on Friday night :)

[jrandallsexton]

Please note that this has been changed to:
jspm registry config github

[plwalters]

@jrandallsexton thx for updating here - the docs should already show the correct usage.

[trusktr]

I'm getting

warn Error on download for github:MikeMcl/bignumber.js
     Error: GitHub rate limit reached.

err  Error downloading github:MikeMcl/bignumber.js.

which doesn't even show a hint about what to do about it.

@guybedford When will this abomination be fixed? Do you even care about the very poor user experience that this causes? Here's proof of the poor user experience, right on Google. Is it your goal to have less users than you could have? Do you think everyone wants to create a GitHub account just so they can use a tool like JSPM? No!

It's been over a year since we've been having this problem (yes, it is a problem, not a feature).

I know as well as you do that you don't need to use api.github.com by default, so that we can avoid this problem altogether, and that you can simply just clone a repo or grab releases from the regular HTTP endpoint (f.e. with URLs like "https://github.com/infamous/motor/archive/v0.0.2.zip") instead of fetching release archives through the API (which hardly anyone uses anyways!!!). I know there's no rate limit because I can run wget in a while loop and download the release from https://github.com/infamous/motor/archive/v0.0.2.zip over and over and over with no problems. Every once in a blue moon I'll get ERROR 429: Too Many Requests., but at least it won't be blocked like with GitHub API rate limits.

The most disappointing feeling when trying to work on something is when using a tool (like JSPM) that seems really awesome (because it is in many respects), then encountering such a crap error. I'm sorry, but this is a horrible design bug that you've made and that you refuse to acknowledge for whatever personal reasons you may have.

I'm sorry if I come off upset, angry, or rude, but it's been over a year since I've been aware of people complaining about this issue, and you just don't care to fix it.

I'm switching any of my projects that use JSPM away from JSPM today, right now, because I don't want to waste any more valuable time with JSPM. JSPM is the only package manager / build system that I've ever wasted so much time with, (I'm not exaggerating).

@EisenbergEffect If I were you I'd consider taking Aurelia to a different build system for the sake of attracting more users.

[guybedford]

@trusktr which version of jspm are you using here? We did specifically work on this user experience so it automatically prompts to set the credentials when this happens. In addition the need for GitHub auth is removed in the coming jspm 0.17. Since this is a breaking change though, we need to manage that upgrade path and couldn't just shift it out with jspm 0.16.

[trusktr]

I just used the latest from NPM, 0.16.19.

Again, sorry for my obvious frustration. It stems from the fact that JSPM is in concept really awesome, but in practice has been time consuming due to the caveats. I really do hope all the things about JSPM can be polished sooner than later, and if anything feature that makes usability better and easier is ready, just release it without caring so much about which which version it will be put in.

I'd recommend that instead of grouping up a lot of features and planning for them to be specifically released at 0.17, just push the features out when they're ready and bump the number. You might end at 0.20 or 0.25 instead of 0.17, but honestly I don't think your users will care about that as much as they'll care about the benefits of the features. If a feature is ready, just get it out there.

In my case, the GitHub authentication problem isn't as simple as myself having to provide my username and password. I don't want to store credentials locally, and I also would have to spend the time to set up GitHub tokens and determine which permissions they shall have, which is time consuming. I think this is fine when the use case is, for example, setting up a hook on a server. The expectation I had with JSPM was to just jspm install whatever I needed and get to deving quickly.

I wish the best for JSPM and hope it becomes an easy to use powerful tool. I'll keep an eye out for JSPM in the future, but for now I'll be on Webpack in order to move on from app build systems towards spending as much time as I can developing apps themselves. I was able to migrate my projects to NPM+Webpack for now, which is working nicely (I just copy my Babel 6 webpack.config.js from project to project).

[guybedford]

@trusktr then you would have got an inline authentication prompt to enter your credentials? When generating a token the exact auth permissions options to set are included in this prompt. An issue for automatic token generation has also been tracking at jspm/jspm-cli#848 to make this easier, and contributions are always welcomed. It is certainly a friction point that is being removed in the coming release this month. Breaking changes are bulked together with clear deprecation paths because of user stability and to removing frustration.

As a user, open source only works when you put some tiny constructive effort towards solutions to your friction points for those who come after you. While it seems it has done nothing to dissuade your need to badmouth the project, I hope you can appreciate at some level the amount of support you have been given on the jspm project over this past year.

[trusktr]

then you would have got an inline authentication prompt to enter your credentials?

There was no prompt. Maybe it's because of the -y option?

I hope you can appreciate at some level the amount of support you have been given on the jspm project over this past year.

I do, which is why I'm keeping an eye on it and not forgetting about it completely. I want to see a concept like JSPM succeed. Urging for basic changes towards that effect but not having seen the changes despite a whole year led to my own pain point.

[eastlondoner]

This jspm github timeout is hitting me on DockerHub builds - putting my github credentials into my dockerfile just to support this is a massive pain! Please fix this!

[EisenbergEffect]

Please report this to jspm. It's completely beyond our control.

[eastlondoner]

sorry! I thought this was jspm