You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[nuxt] Error while initializing app Error: Loading chunk 6 failed.
I'm getting the same error after build and start
I'm using the express server example and router mode as history
I don't know how to reproduce this on a small project.
I can tell that in Network inspector I see /_nuxt/pages/.37ce4084c1c2cef60da2.js cannot be found (404 Not Found)
@vinhtq I was thinking of that, I'm planning to start a clean project and keep adding things one by one to see the breaking point but don't know if it's worth it.
Thanks @vinhtq it was the chunk routes name as described in #1461
I had to use a router template, that's the danger of making router manually to support language routes
I also experience it in latest version(V1.3x). In development mode, it is ok, but in production mode, you can meet this error sometimes.
I have no idea how to fix it~
This is due to code-splitting and would produce the same on any Vue application.
The only solution is to keep the old files when deploying the new app, so the best is to upload to a CDN every time you deploy, so the old files are not deleted.
But I guess what we can do is to check this error and do a hard reload to avoid doing so? cc @pi0@clarkdo
TheAlexLichter, thenickname, HoraceKeung, benoitemile and RDeluxe
I'm trying to implement the solution provided by @yoyo837 but having some platform specific issues so here's to hoping someone has a better grasp on this..
I'm hosting my app on heroku which runs the "yarn run build"-command in the heroku-postbuild script, building all the files to the ".nuxt/dist"-folder. When I run it locally I can access the "dist"-folder w/o any problem.
However; runtime in heroku the dist-folder doesn't seem to exist in the ".nuxt"-folder:
Activity
atinux commentedon May 20, 2017
Hi @alekseyLymarev
Please provide a repository to reproduce this error or an example online by forking https://glitch.com/edit/#!/nuxt-hello-world.
Then I'll re-open the issue.
alekseyLymarev commentedon May 20, 2017
Well as soon as I can reproduce the error I will send you, it appears periodically.
epartipilo commentedon Sep 19, 2017
Hi @atinux
[nuxt] Error while initializing app Error: Loading chunk 6 failed.
I'm getting the same error after
build
andstart
I'm using the express server example and router mode as
history
I don't know how to reproduce this on a small project.
I can tell that in Network inspector I see
/_nuxt/pages/.37ce4084c1c2cef60da2.js
cannot be found (404 Not Found
)I also see this on terminal when building
Hope this can give a clue on this issue
Thanks!
vinhtq commentedon Oct 5, 2017
I have same issue. When the app get bigger, more code will be compiled from webpack.
Then you will get this error more often. Not sure how to fix this!
epartipilo commentedon Oct 5, 2017
@vinhtq I was thinking of that, I'm planning to start a clean project and keep adding things one by one to see the breaking point but don't know if it's worth it.
Cheers!
vinhtq commentedon Oct 5, 2017
The new version of nuxtjs RC11 talking some fixes about this issue
Try to update to the latest version to see if the issue still exists
epartipilo commentedon Oct 5, 2017
I'm still getting the error.
I'll do the decompose thing because it's been a roller coaster experimental project.
Thanks!
epartipilo commentedon Oct 31, 2017
Thanks @vinhtq it was the chunk routes name as described in #1461
I had to use a router template, that's the danger of making router manually to support language routes
xxxxxMiss commentedon Feb 9, 2018
I also experience it in latest version(V1.3x). In development mode, it is ok, but in production mode, you can meet this error sometimes.
I have no idea how to fix it~
campope commentedon Feb 24, 2018
I'm having this issue as well anyone know any solutions?
epartipilo commentedon Feb 26, 2018
@campope did you configure your router manually?
campope commentedon Feb 26, 2018
Nope running in universal mode using only page and folder names for routes.
TheAlexLichter commentedon Mar 12, 2018
Experiencing this issue as well
18 remaining items
yoyo837 commentedon May 26, 2018
@tctimmeh Yes, I modified error.vue to identify this error and refresh it automatically to fixed this issue.
aldarund commentedon May 31, 2018
@yoyo837 i guess something like that should be implemented in nuxt itself. Can you share your code for identifying this error?
atinux commentedon Jun 1, 2018
This is due to code-splitting and would produce the same on any Vue application.
The only solution is to keep the old files when deploying the new app, so the best is to upload to a CDN every time you deploy, so the old files are not deleted.
But I guess what we can do is to check this error and do a hard reload to avoid doing so? cc @pi0 @clarkdo
yoyo837 commentedon Jun 1, 2018
@aldarund
my code:
layouts/error.vue
global :
server/index.js
:atinux commentedon Aug 6, 2018
Discussion going on: #3389
feload commentedon Aug 21, 2018
I solved it on my end by prepending a dot to "publicPath" outuput option in my webpack config file.
alexpilugin commentedon Sep 19, 2018
The same issue.
b3itgustaf commentedon Sep 21, 2018
I'm trying to implement the solution provided by @yoyo837 but having some platform specific issues so here's to hoping someone has a better grasp on this..
I'm hosting my app on heroku which runs the "yarn run build"-command in the heroku-postbuild script, building all the files to the ".nuxt/dist"-folder. When I run it locally I can access the "dist"-folder w/o any problem.
However; runtime in heroku the dist-folder doesn't seem to exist in the ".nuxt"-folder:
[
'App.js',
'client.js',
'components',
'index.js',
'empty.js',
'google-tag-manager.js',
'router.js',
'server.js',
'loading.html',
'middleware.js',
'store.js',
'utils.js',
'views'
]
.. So:
I'll admit I'm not all to experienced in Heroku hosting but surely the dist folder must exist because the site works perfectly.
Anyone has a handle on this?
lock commentedon Oct 31, 2018
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
fix(editor): inline emojis correctly