Nuxt.js: Broken in chrome 41

Created on 6 Apr 2018  路  6Comments  路  Source: nuxt/nuxt.js

Version

v1.4.0

Reproduction link

https://www.e-lens.com.br/

Steps to reproduce

Open in chrome 41
Screenshot from 2018-04-05 19-03-34.png

What is expected ?

Solution

What is actually happening?

Broken in chrome 41, it's same version which google use to crawler

This bug report is available on Nuxt.js community (#c6858)
bug-report

Most helpful comment

Hi @joaocarvalhowd

Actually, I tried with Chrom 41 and I have another error:

Screen Shot 2018-04-10 at 09.36.07.png

The error about client-side not matching is when you have client-side script or even Chrome that update the rendered HTML before Vue hydration, it might be because of a phone number for example.

You can update the babel env in your nuxt.config.js:

module.exports = {
  build: {
    babel: {
      presets({ isServer }) {
        if (isServer) return null // Use default
        return [
          ['vue-app', {
            targets: {
              chrome: 40,
              edge: 9,
              firefox: 40,
              ie: 9,
              safari: 7
            }
          }]
        ]
      }
    }
  },
};

All 6 comments

Same happen here.

Link to reproduce: https://www.browserling.com/browse/win/7/chrome/41/https%3A%2F%2Fcotabox.com.br

screenshot from 2018-04-05 19-11-09

I can't use the website, all links does not open and components not react to click.

@pi0

Hi @joaocarvalhowd

Actually, I tried with Chrom 41 and I have another error:

Screen Shot 2018-04-10 at 09.36.07.png

The error about client-side not matching is when you have client-side script or even Chrome that update the rendered HTML before Vue hydration, it might be because of a phone number for example.

You can update the babel env in your nuxt.config.js:

module.exports = {
  build: {
    babel: {
      presets({ isServer }) {
        if (isServer) return null // Use default
        return [
          ['vue-app', {
            targets: {
              chrome: 40,
              edge: 9,
              firefox: 40,
              ie: 9,
              safari: 7
            }
          }]
        ]
      }
    }
  },
};

@Atinux We found the problem the real problem. And we managed to solve it.
https://github.com/zeit/next.js/issues/3529

Thanks for trying to help us 馃槃

I tried both @joaocarvalhowd and @Atinux and I still get this error: TypeError: undefined is not a function

To reproduce: https://www.browserling.com/browse/win/7/chrome/41/https%3A%2F%2Fcotabox.com.br

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.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

vadimsg picture vadimsg  路  3Comments

mikekidder picture mikekidder  路  3Comments

msudgh picture msudgh  路  3Comments

danieloprado picture danieloprado  路  3Comments

nassimbenkirane picture nassimbenkirane  路  3Comments