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

Repo jspm:systemjs-hot-reloader not found #111

Closed
FDiskas opened this issue Oct 28, 2016 · 12 comments
Closed

Repo jspm:systemjs-hot-reloader not found #111

FDiskas opened this issue Oct 28, 2016 · 12 comments

Comments

@FDiskas
Copy link

FDiskas commented Oct 28, 2016

$ jspm -v
0.16.47
@lancecarlson
Copy link

I have the same issue.

@capaj
Copy link
Collaborator

capaj commented Oct 30, 2016

I just installed fine. I would suspect this will have something to do with your network or some error in JSPM's own repository resolution. Can you try again @FDiskas @lancecarlson ? Also can you try some other jspm package defined in https://github.com/jspm/registry/blob/master/registry.json ?

@lancecarlson
Copy link

$ jspm i --dev systemjs-hot-reloader

err Repo jspm:systemjs-hot-reloader not found. Perhaps try jspm install npm:systemjs-hot-reloader.

warn Installation changes not saved.
[lcarlson@localhost ecp_example]$ jspm i --dev npm:systemjs-hot-reloader
Looking up npm:systemjs-hot-reloader
Downloading npm:systemjs-hot-reloader@0.6.0

warn Error on processPackageConfig
Package.json dependency debug set to npm:debug@^2.2.0, which is not a valid dependency format for npm.
It's advisable to publish jspm-style packages to GitHub or another registry so conventions are clear.
To skip npm compatibility install with jspm install npm:systemjs-hot-reloader@0.6.0-o "{jspmPackage: true}".

warn Error processing package config for npm:systemjs-hot-reloader.

err Error processing package config for npm:systemjs-hot-reloader.

warn Installation changes not saved.

@born2net
Copy link

so do we need to run hot-reload in a diff way now? with these changes?
I use it with Angular2
regards

Sean

@lancecarlson
Copy link

I've also tried on 4 different networks. Same issue.

@capaj
Copy link
Collaborator

capaj commented Oct 31, 2016

@born2net no, it should still be usable as before. We haven't even released any new version. And even when 0.7.0 comes out, it won't change the way you use it.

@FDiskas
Copy link
Author

FDiskas commented Oct 31, 2016

'lodash' the same. jspm install lodash

@born2net
Copy link

great tx

@capaj
Copy link
Collaborator

capaj commented Oct 31, 2016

@FDiskas the same problem when installing lodash? Well then it seems like a bug for @guybedford Maybe you could try some older version of JSPM in the meantime. I'd guess 0.16.30ish could be better

@alexisvincent
Copy link
Owner

@FDiskas @lancecarlson Still have this issue?

@lancecarlson
Copy link

@alexisvincent sorry, I've since moved on from this! Not sure if this is an issue anymore. :(

@alexisvincent
Copy link
Owner

Cool thanks

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

5 participants