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

Upgrading the beta 6: Registry returned 404 for GET on https://registry.npmjs.org/angular-cli-inject-live-reload #1122

Closed
sharpmachine opened this issue Jun 17, 2016 · 10 comments · Fixed by #1128
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix

Comments

@sharpmachine
Copy link

sharpmachine commented Jun 17, 2016

Went through the steps to upgrade from beta 5 to 6. When going through the ng init step, I removed the ember-cli-inject-live-reload from package.json and replaced it with "angular-cli-inject-live-reload": "1.4.0", as suggested, and also updated my index.html to:

  {{#unless environment.production}}
  <script src="/angular-cli-live-reload.js"
      type="text/javascript"></script>
  {{/unless}}

But when the cli installs all the tooling, it fails with:
Registry returned 404 for GET on https://registry.npmjs.org/angular-cli-inject-live-reload

OSX El Capitan
angular-cli: 1.0.0-beta.6
node: 5.11.1
os: darwin x64

@nosachamos
Copy link

nosachamos commented Jun 17, 2016

@sharpmachine Interestingly, I'm on alpha 6 and ng new will install ember-cli-inject-live-reload, not angular-cli-inject-live-reload. It may be that if you just undo this particular change, you'll be fine.

BTW, google finds no matches for "angular-cli-inject-live-reload"... this was probably a bogus upgrade tip hehe try reverting to the ember package.

@sharpmachine
Copy link
Author

sharpmachine commented Jun 17, 2016

@nosachamos. I'm on beta 6....not alpha. It was release a few days ago. I tried reverting back to the ember-cli-inject-live-reload but now when I run ng-serve I get:

Could not require 'angular-cli-build.js': Unexpected string
SyntaxError: Could not require 'angular-cli-build.js': Unexpected string
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:387:25)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at module.exports (/Users/jessekuntz/Projects/NSG.CMS/NSG.CMS.Client.Web/node_modules/angular-cli/node_modules/angular-cli/lib/utilities/find-build-file.js:21:17)
    at patchedFindBuildFile (/Users/jessekuntz/Projects/NSG.CMS/NSG.CMS.Client.Web/node_modules/angular-cli/lib/cli/index.js:53:42)
    at Class.module.exports.Task.extend.setupBroccoliBuilder (/Users/jessekuntz/Projects/NSG.CMS/NSG.CMS.Client.Web/node_modules/angular-cli/node_modules/angular-cli/lib/models/builder.js:49:21)

I hope someone on the Angular CLI team gets back to me soon kuz I can't do any work until I fix this.

@nosachamos
Copy link

Ops, I meant beta 6.

Well, that sucks. I suspect doing a ng new and then porting your project to a brand new shell is not an option, right? It's a bit of work, but if you're blocked it's hard to imagine that'd be worst.

@sharpmachine
Copy link
Author

That's a LOT of work...the issue is that there is no angular-cli-inject-live-reload package in NPM. It doesn't exist. So the only think I can do is try to roll back to beta.5 until someone from the team gets back to me. Usually they respond quickly but they must be on vacation or something.

@sharpmachine
Copy link
Author

It's weird because if I generate a new project, it uses the ember-cli-livereload.

@sharpmachine
Copy link
Author

sharpmachine commented Jun 17, 2016

? Overwrite src/index.html? Diff

@@ -1,70 +1,31 @@
...
+  {{#unless environment.production}}
+  <script src="/angular-cli-live-reload.js" type="text/javascript"></script>{{/unless}}
...
? Overwrite package.json? Diff
...
-    "angular-cli-inject-live-reload": "^1.4.0",
+    "angular-cli-inject-live-reload": "1.4.0",
...

But it's weird because my actual package.json that it want's to overwrite is:

...
"ember-cli-inject-live-reload": "1.4.0",
...

The diff doesn't even see ember-cli-inject...it's like it wants to read it as 'angular-cli-inject

@Splaktar
Copy link
Member

@sharpmachine It needs to be ember-cli-inject-live-reload. As stated by @nosachamos, there is no angular-cli-inject-live-reload.

I removed the ember-cli-inject-live-reload from package.json and replaced it with "angular-cli-inject-live-reload": "1.4.0", as suggested

This is not suggested by the docs. You are saying that the diff suggested it and/or the overwrite suggested it? I just did the upgrade and I'm not seeing that behavior on OS X.

@sharpmachine
Copy link
Author

@Splaktar

Yes, I'm saying that the diff suggested it. I copied/pasted the output from the ng init step of the upgrade. Angular CLI wanted to replace ember-cli-live-reload with angular-cli-live-reload in the package.json and index.html. This was on a current project, not a new one.

@filipesilva
Copy link
Contributor

Ugh, this is an unintended side effect of a filter we put in to remove ember-cli branding from leaking. There is no angular-cli-inject-live-reload, it should be ember-cli-inject-live-reload instead.

@filipesilva filipesilva added type: bug/fix P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful labels Jun 18, 2016
filipesilva added a commit to filipesilva/angular-cli that referenced this issue Jun 18, 2016
adriancarriger added a commit to adriancarriger/pv-site that referenced this issue Jun 26, 2016
After upgrading to Angular Cli  1.0.0-beta.6 there was  a 404 for livereload during development. Angular Cli issue [#1122](angular/angular-cli#1122)
emma-mens pushed a commit to emma-mens/angular-cli that referenced this issue Jul 1, 2016
emma-mens pushed a commit to emma-mens/angular-cli that referenced this issue Jul 1, 2016
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants