Browser tab stalled on application load.

[levibostian]

I upgraded my site to the newest version of nuxtent (v0.2.57). When I run nuxt build, my site successfully builds and the command succeeds.

When I then run nuxt start, my nuxt server starts up successfully and listens for me to connect.

When I open my browser, open up to 127.0.0.1:3000/ like I have it configured to, I successfully call the nuxt web server and it begins fetching data and rendering to me successfully. This is good because in a previous version of nuxtent, my site was not working giving me the error:

site_1  | [Vue warn]: Error in render function: "TypeError: Cannot read property 'sort' of undefined"
site_1  |
site_1  | found in
site_1  |
site_1  | ---> <Anonymous>
site_1  |        <Nuxt>
site_1  |          <Anonymous>
site_1  |            <Root>

This seems to be solved in the newest version of nuxtent. However, my browser tab seems to stall. My application in the browser runs out of memory. The progress bar of my browser tab continuously spins, I cannot scroll at all, cannot click anything on my webpage. I cannot do anything. I open up the console, nothing is outputting.

If I close the browser tab within ~5 seconds I am able to wait a couple seconds and then my browser will close the tab. If I wait >10 seconds, however, my browser gets killed. I cannot go to different tabs, I cannot do anything with my browser and I have to force kill the tab.

The output of nuxt doesn't seem to be too weird:

/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
/content-api GET http://127.0.0.1:3000/
   Response sent successfully.
  nuxt:render Data fetching /: 186ms +191ms
  nuxt:render Rendering url /undefined +1s
/content-api GET http://127.0.0.1:3000/undefined
   Page not found.
  nuxt:render Data fetching /undefined: 8ms +14ms

No warnings or errors.

You can pull/view my code on this branch and this commit to see for yourself if you wish.

_{This question is available on Nuxt.js community (#c35)}

[levibostian]

Also, I should note another weird behavior of nuxtent with the newest version.

When I am running nuxt dev mode and I load up my application's homepage, I am getting the same symptoms I was having here with this issue where my application's data disappears when the webpage loads. I am not using <nuxtent-body/> like this issue mentions, but my body is still being collapsed. All my <nuxt> data disappears.

You can pull/view my code on this branch and this commit to see for yourself if you wish.

[alidcast]

I'll look into this fully over the next couple days, hopefully, sooner.

Can you give me more context - does this happen in a specific page route or upon initial rendering?

Also, side note, make sure that you're using alpha 3 version of Nuxt, as rc3 is not fully working yet.

[levibostian]

Ok, I was not running on nuxtjs alpha3. I was on rc3. After switching to alpha3 on this commit I am still running the same issue.

More context: it happens on the home page and on any of the pages that I have tried so far (/freelance, /opensource). Run npm run build, npm run start, then open up 127.0.0.1:3000/, 127.0.0.1:3000/freelance, 127.0.0.1:3000/opensource on your browser. The webpage will render to you so you think it's working, but then you notice you cannot do anything and eventually have to kill your browser.

[alidcast]

btw Finishing up some final updates today and then will take a look at this

[alidcast]

Hey, so I cloned and ran your project.

I did not experience the browser stalling issue, but there was some weird behavior on the index page which seems to be unrelated to nuxtent cause by this script : script#-clp-1502(async='', src='https://withcoach.com/landing_pages/1502/embed.js'). Side note: I also saw that you were using pug mixins. I would aim to use Vuejs props, computed properties, v-for directives instead, as maybe that's causing problems.

Nuxtent seems to be working as it should: I can go to content-api/freelance see all the content. I can go to freelance route and see the projects.

[alidcast]

I'm going to go ahead and close this issue, feel free to open it back up or open another one if you still experience a problem with Nuxtent, but I'd need a smaller reproducible issue as the clutter of a full site made it difficult to test.

[alidcast]

Btw, in next release, if you have multiple content types, you'll be able to go to content-api and see all the registered content endpoints, so that you can see if the content is being compiled and loaded, or not.

It took me a while to realize Nuxtent was working since content-api was returning a 404. 😅