Skip to content

webpackJsonp is not defined #8245

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

Closed
doovers opened this issue Oct 29, 2017 · 4 comments
Closed

webpackJsonp is not defined #8245

doovers opened this issue Oct 29, 2017 · 4 comments

Comments

@doovers
Copy link

doovers commented Oct 29, 2017

Bug Report or Feature Request (mark with an x)

- [x] bug report
- [ ] feature request

Versions.

@angular/cli: 1.4.9
node: 6.10.3
os: darwin x64
@angular/animations: 4.4.6
@angular/cdk: 2.0.0-beta.12
@angular/common: 4.4.6
@angular/compiler: 4.4.6
@angular/core: 4.4.6
@angular/forms: 4.4.6
@angular/http: 4.4.6
@angular/material: 2.0.0-beta.12
@angular/platform-browser: 4.4.6
@angular/platform-browser-dynamic: 4.4.6
@angular/router: 4.4.6
@angular/cli: 1.4.9
@angular/compiler-cli: 4.4.6
@angular/language-service: 4.4.6
typescript: 2.3.4

Repro steps.

Not sure how to reproduce. The issue shows up intermittently.

The log given by the failure.

[Error] ReferenceError: Can't find variable: webpackJsonp
Global Code (polyfills.bundle.js:1)
[Error] ReferenceError: Can't find variable: webpackJsonp
Global Code (styles.bundle.js:1)
[Error] ReferenceError: Can't find variable: webpackJsonp
Global Code (vendor.bundle.js:1)

@avbentem
Copy link

avbentem commented Nov 8, 2017

That's not a lot of detail to go on.

See also #8026.

Any chance you're not using the default index.html in which the required JavaScript bundles are inserted automatically, but instead are using some other means to insert the bundles?

(If yes, then see https://stackoverflow.com/a/41829100.)

@doovers
Copy link
Author

doovers commented Nov 13, 2017

@avbentem Yes, apologies for the lack of detail I was in a bit of a rush posting and was hoping it might be an obvious fix for someone! To elaborate a little it occurs in one of 2 almost identical components. It renders the page the first time around but if I hit refresh, it will give me those errors. If I go back a page and navigate to it again it will render properly again. The same error occurs if I make a change to a file and it reloads. Hopefully, that clarifies things a little? Oh and I'm using the default index.html. No customisations there...

@filipesilva
Copy link
Contributor

I think this issue is a duplicate of #8026. Can you add a repro and details there please? With just the information here there isn't much we can do to address it.

@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants