V-calendar: ERROR: js was blocked due to mime type (“text/html”) mismatch after update to 1.0.0-beta.17 from 1.0.0-beta.16

[solankivj]

[solankivj]

The resource from “http://demo/v-calendar.umd.min.v-calendar.js” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).

      return Promise.all([o.e(0), o.e(2)]).then(o.bind(null, "e94a"));
    }

Reason: Error: Loading chunk 0 failed.
(error: http://demo/v-calendar.umd.min.v-calendar.js)

[d-koppenhagen]

Same here

[ptdev]

Hi,

I have the same issue after upgrading to beta.17 without any other changes.

GET http://localhost:3001/_nuxt/v-calendar.umd.min.v-calendar.js net::ERR_ABORTED 404 (Not Found)
GET http://localhost:3001/_nuxt/v-calendar.umd.min.v-date-picker.js net::ERR_ABORTED 404 (Not Found)
error [Vue warn]: Failed to resolve async component: ()=>Promise.all([o.e(0),o.e(2)]).then(o.bind(null,"e94a"))
Reason: Error: Loading chunk 0 failed.
(error: http://localhost:3001/_nuxt/v-calendar.umd.min.v-calendar.js)

[nathanreyes]

You shouldn’t use this version as Webpack is unable to resolve dynamic import chunks from 3rd party packages. I thought I had removed the ‘next’ tag from it but it seems I may need to unpublish it from npm. Beta 18 will get released soon to address the latest updates but unfortunately won’t be able to have dynamic imports for the popover component.

[ikoukuhn]

So, which version should we use to avoid this issue?

[nathanreyes]

1.0.0-beta.19