We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
parseResource always marks all scripts as modules:
parseResource
vue-bundle-renderer/src/utils.ts
Lines 52 to 63 in 2016345
This in turn affects normalizeViteManifest which emits all script chunks as having module: true:
normalizeViteManifest
module: true
vue-bundle-renderer/src/vite.ts
Lines 5 to 10 in 2016345
Then, renderScripts always emits <script type="module"> preventing legacy browsers from even loading the code:
renderScripts
<script type="module">
vue-bundle-renderer/src/runtime.ts
Lines 234 to 237 in 253407e
See nuxt/bridge#621 for the actual user-facing issue.
The text was updated successfully, but these errors were encountered:
I think this is just meant to be the default. What we need to do in Nuxt Bridge is explicitly modify the manifest to mark module: false.
module: false
Sorry, something went wrong.
No branches or pull requests
parseResource
always marks all scripts as modules:vue-bundle-renderer/src/utils.ts
Lines 52 to 63 in 2016345
This in turn affects
normalizeViteManifest
which emits all script chunks as havingmodule: true
:vue-bundle-renderer/src/vite.ts
Lines 5 to 10 in 2016345
Then,
renderScripts
always emits<script type="module">
preventing legacy browsers from even loading the code:vue-bundle-renderer/src/runtime.ts
Lines 234 to 237 in 253407e
See nuxt/bridge#621 for the actual user-facing issue.
The text was updated successfully, but these errors were encountered: