tauri refuses to read frontendDist when running yarn/npm build

[yemmlie]

Hi! I want to ask about this here prior to posting as a bug since its very possible i'm doing something wrong but i can't possibly see what at this point.

I have a tauri app with a vite frontend. It works perfectly fine in dev, and in the past I definitely bundled it to a release exe, though this may have been with tauri v1.

My tauri.conf.json has the following:

"build": {
   "beforeDevCommand": "yarn dev",
   "devUrl": "http://localhost:5173",
   "beforeBuildCommand": "yarn build",
   "frontendDist": "../dist"
 },

When building I get the following error:

error during build:
Could not resolve entry module "tauri/index.html".
    at getRollupError (file:///node_modules/rollup/dist/es/shared/parseAst.js:395:41)
    at error (file:///node_modules/rollup/dist/es/shared/parseAst.js:391:42)
    at ModuleLoader.loadEntryModule (file:///node_modules/rollup/dist/es/shared/node-entry.js:20027:20)
    at async Promise.all (index 0)
    

(deleted start of paths for privacy reasons)

So its just refusing to accept the parameter ../dist as my folder. I've created a new tauri v2 app in a separate directory and compared the entire projects and see no reason why this would happen.

Furthermore, when I manually copy my dist folder to tauri folder so that the folder is where it expects, the build fails due to browser incompatiblities with chrome etc, however in my vite.config.ts I have already dealt with these build errors with:

  build: {
    target: "esnext", 
  },

Which allows my build to compile perfectly fine with 'yarn build', so it feels like tauri is completely ignoring my vite.config.ts as well.

Structurally all my folder structures, config files and everything match the default skeleton app created from cli, I've cleared out my node_modules and lock files, I've done everything I can think of, I've scoured the net for a similar issue and found nothing.

At the end of my rope I've been bashing my head against this for two days now and in a situation where I'm worried i can't distribute what I'm working on because i can't make a release build.

[FabianLars]

So its just refusing to accept the parameter ../dist as my folder.

Well, no. This error is vite failing to build your frontend. The frontendDist config is only relevant after the frontend build succeeded.

Which allows my build to compile perfectly fine with 'yarn build', so it feels like tauri is completely ignoring my vite.config.ts as well.

This also doesn't really make sense because tauri simply runs the beforeBuildCommand without doing anything special.

Can you maybe share your whole vite config? And also the file structure (at least for the html file(s) since it's complaining about it) if possible.

[yemmlie]

Thanks for the response!

So it appears I was firing off tauri build with a noobie mistake and it was interpreting 'tauri' as a parameter to the build, so the /tauri/ thing is sorted. but now I'm still left with the other strange issue of it ignoring a parameter in my vite.config.ts that makes the project build successfully.

Relevant folder structure:

D:\Code\projectRoot\index.html
D:\Code\projectRoot\package.json
D:\Code\projectRoot\tsconfig.json
D:\Code\projectRoot\tsconfig.node.json
D:\Code\projectRoot\vite.config.ts
D:\Code\projectRoot\node_modules
D:\Code\projectRoot\src\
D:\Code\projectRoot\dist\
D:\Code\projectRoot\src-tauri\
D:\Code\projectRoot\src-tauri\tauri.conf.json
D:\Code\projectRoot\src-tauri\Cargo.toml

If I go into my powershell and type in

yarn build

it provides this output:

Done in 0.22s.
PS D:\Code\projectRoot> yarn build
yarn run v1.22.22
$ tsc && vite build
vite v5.4.10 building for production...
✓ 11752 modules transformed.
dist/index.html                     2.81 kB │ gzip:   0.66 kB
dist/assets/index-D5KajLQj.css     24.41 kB │ gzip:   4.91 kB
dist/assets/index-CP8D9mYo.js   1,211.90 kB │ gzip: 387.59 kB

(!) Some chunks are larger than 500 kB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✓ built in 14.09s
Done in 19.64s.```

and adds the following files:

D:\Code\projectRoot\dist\index.html

D:\Code\projectRoot\dist\favicon.ico

D:\Code\projectRoot\dist\assets

D:\Code\projectRoot\dist\assets\index-CP8D9mYo.js

D:\Code\projectRoot\dist\assets\index-D5KajLQj.css

Content of D:\Code\projectRoot\vite.config.ts with added line for esnext that makes 'yarn build' work fine:

import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";

// @ts-expect-error process is a nodejs global
const host = process.env.TAURI_DEV_HOST;

// https://vitejs.dev/config/
export default defineConfig(async () => ({
  plugins: [react()],

  // Vite options tailored for Tauri development and only applied in `tauri dev` or `tauri build```
  //
  // 1. prevent vite from obscuring rust errors
  clearScreen: false,
  // 2. tauri expects a fixed port, fail if that port is not available
  server: {
    port: 5173,
    strictPort: true,
    host: host || false,
    hmr: host
      ? {
          protocol: "ws",
          host,
          port: 5173,
        }
      : undefined,
    watch: {
      // 3. tell vite to ignore watching `src-tauri```
      ignored: ["**/src-tauri/**"],
    },
    build: {
      target: "esnext",       // <--- ADDED THIS TO MAKE BUILD SUCCESSFUL
    },
  },
}));

contents of D:\Code\projectRoot\src-tauri\tauri-conf.json

{
  "$schema": "https://schema.tauri.app/config/2",
  "productName": "productName",
  "version": "0.1.0",
  "identifier": "com.yemmlie.dev",
  "build": {
    "beforeDevCommand": "yarn dev",
    "devUrl": "http://localhost:5173",
    "beforeBuildCommand": "yarn build",
    "frontendDist": "../dist"
  },
  "app": {
    "withGlobalTauri": true,
    "windows": [
      {
        "fullscreen": false,
        "height": 1080,
        "resizable": true,
        "title": "Product Title",
        "width": 1920,
        "maximized": true,
        "dragDropEnabled": false
      }
    ],
    "security": {
      "csp": null
    }
  },

  "bundle": {
    "active": true,
    "targets": "all",
    "icon": [
      "icons/32x32.png",
      "icons/128x128.png",
      "icons/128x128@2x.png",
      "icons/icon.icns",
      "icons/icon.ico"
    ]
  }
}

output if I type run

yarn build tauri

is

PS D:\Code\projectRoot> yarn tauri build
yarn run v1.22.22
$ tauri build
    Running beforeBuildCommand `yarn build`
$ tsc && vite build
vite v5.4.10 building for production...
✓ 11752 modules transformed.
x Build failed in 13.59s
error during build:
[vite:esbuild-transpile] Transform failed with 2 errors:
assets/index-!~{001}~.js:72338:0: ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
assets/index-!~{001}~.js:72341:0: ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)

Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)

    at failureErrorWithLog (D:\Code\projectRoot\node_modules\esbuild\lib\main.js:1472:15)
    at D:\Code\projectRoot\node_modules\esbuild\lib\main.js:755:50
    at responseCallbacks.<computed> (D:\Code\projectRoot\node_modules\esbuild\lib\main.js:622:9)
    at handleIncomingPacket (D:\Code\projectRoot\node_modules\esbuild\lib\main.js:677:12)
    at Socket.readFromStdout (D:\Code\projectRoot\node_modules\esbuild\lib\main.js:600:7)
    at Socket.emit (node:events:520:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at Pipe.onStreamRead (node:internal/stream_base_commons:191:23)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
beforeBuildCommand `yarn build` failed with exit code 1
    Error beforeBuildCommand `yarn build` failed with exit code 1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
PS D:\Code\projectRoot>

Of particular relevance is:

error during build:
[vite:esbuild-transpile] Transform failed with 2 errors:
assets/index-!~{001}~.js:72338:0: ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
assets/index-!~{001}~.js:72341:0: ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)

which I avoid in my vite config, and yarn build works just fine, after I added the target "esnext" into it.

...but I just also noticed the error is ending in the following:

    at failureErrorWithLog (D:\Code\projectRoot\node_modules\esbuild\lib\main.js:1472:15)
    at D:\Code\projectRoot\node_modules\esbuild\lib\main.js:755:50
    at responseCallbacks.<computed> (D:\Code\projectRoot\node_modules\esbuild\lib\main.js:622:9)
    at handleIncomingPacket (D:\Code\projectRoot\node_modules\esbuild\lib\main.js:677:12)
    at Socket.readFromStdout (D:\Code\projectRoot\node_modules\esbuild\lib\main.js:600:7)
    at Socket.emit (node:events:520:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at Pipe.onStreamRead (node:internal/stream_base_commons:191:23)

which seems like the log is bugging out and crashing am not sure if this is expected.

[yemmlie]

I just bit the bullet and worked around not having top level asyncs to resolve the issue of needing esnext. It adds complications and makes things a lot more difficult considering i'm making what is essentially a desktop app having a couple of awaits wasn't hurting anything but I've ran out of steam with this.

No idea what was causing it. Thanks for your reply