nuxt / vite

⚡ Vite Experience with Nuxt 2

Home Page:https://vite.nuxtjs.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Transforming destructuring to the configured target environment is not supported yet

chrispreisler opened this issue · comments

commented

Versions

nuxt-vite: v0.0.36
nuxt: v2.15.3

Reproduction

https://codesandbox.io/s/beautiful-cohen-7fc42?file=/nuxt.config.js

Description

Hey guys,

I tried to add Nuxt-Vite to a fresh installed nuxt app. Unfortunately I get this errors. It only happens, when ssr is enabled. Is ssr even supported? Above you find a reproduction sandbox link.

Thank you very much for looking into that.

Best regards
Chris

ERROR  Transform failed with 24 errors:                                                                                                                                     15:01:43
server.js:250:10: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
server.js:316:8: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
server.js:317:8: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
server.js:318:8: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
server.js:329:8: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
...

 server.js:250:10: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
 server.js:316:8: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
 server.js:317:8: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
 server.js:318:8: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
 server.js:329:8: error: Transforming destructuring to the configured target environment ("chrome61", "edge16", "es2019", "firefox60", "safari11") is not supported yet
 ...
 at failureErrorWithLog (node_modules/esbuild/lib/main.js:1195:15)
 at node_modules/esbuild/lib/main.js:1056:33
 at node_modules/esbuild/lib/main.js:566:9
 at handleIncomingPacket (node_modules/esbuild/lib/main.js:655:9)
 at Socket.readFromStdout (node_modules/esbuild/lib/main.js:533:7)
 at Socket.emit (events.js:315:20)
 at addChunk (_stream_readable.js:295:12)
 at readableAddChunk (_stream_readable.js:271:9)
 at Socket.Readable.push (_stream_readable.js:212:10)
 at Pipe.onStreamRead (internal/stream_base_commons.js:186:23)

#- [ ] - @💋

Any update? I have same issue.

commented

Same.

Hello, using edge18 or newer as a build target instead of edge16 should work. Here's an example for a standalone vite.config.ts

import vue from '@vitejs/plugin-vue'
import { defineConfig } from 'vite'

export default defineConfig(({ command }) => {
    if (command === 'serve') {
        return {
            plugins: [vue()]
        }
    } else {
        return {
            plugins: [vue()],
            build: {
                target: ['chrome60', 'firefox60', 'safari11', 'edge18'],
            }
        }
    }
})

This can probably be set in nuxt as well (https://vite.nuxtjs.org/getting-started/config) like so (untested):

export default {
  buildModules: [
    'nuxt-vite'
  ],
  vite: {
    build: {
      target: ['chrome60', 'firefox60', 'safari11', 'edge18']
    },
  }
}

Cheers

commented

Same.

Me too :octocat:

#@n

using edge18 or newer as a build target instead of edge16 should work

Not a Vite user, but this solved my issue with this exact error in a standalone esbuild project. Thanks @maurer2!