experiments.optimize.bundle: true -- ENOENT: no such file or directory, unlink /home/p/projects/csa-react/build/build/__snowpack__/env.js

[pschyska]

Hey,

I was using experiments.optimize.bundle: true successfully in a lit-element project (from the csa-lit-element-ts template).
Trying the same with the csa-preact-typescript or csa-react-typescript templates, I'm getting the following error:

ENOENT: no such file or directory, unlink '<snip...>projects/csa-react/build/build/__snowpack__/env.js'

Note the build/build part, which doesn't exist.

Command and output:

± pnpx snowpack build --reload build
[snowpack] ! clearing cache...
[snowpack] ! building source files...
[snowpack] ✔ build complete [0.03s]
[snowpack] ! installing dependencies...
[snowpack] ✔ install complete! [0.88s]
[snowpack] ! verifying build...
[snowpack] ✔ verification complete [0.00s]
[snowpack] ! writing build to disk...
[snowpack] ! optimizing build...
[optimize] (early preview: experiments.optimize is experimental, and still subject to change.)
[snowpack] ENOENT: no such file or directory, unlink '/home/p/projects/csa-react/build/build/__snowpack__/env.js'
-> [1]

My project: npx create-snowpack-app csa-react --template @snowpack/app-template-react-typescript --use-pnpm. Then added optimize to snowpack.config.js:

  experiments: {
    optimize: {
      bundle: true,
      minify: true,
      manifest: true,
      target: "es2020",
    },
  },

Random versions:

node v15.4.0
snowpack: *either* 2.18.4 or 3.0.0-rc.2 without observable difference

(Unsurprisingly the issue goes away when I set bundle: false, because there are no unbundled files to remove then)

This only happens with esbuild 0.8.24, and not 0.8.23. The output format of esbuild's manifest is different:

+{
   "inputs": {
-    "__snowpack__/env.js": {
+    "build/__snowpack__/env.js": {
       "bytes": 97,
       "imports": []
     },
-    "web_modules/common/index-e66f0a38.js": {
+    "build/web_modules/common/index-e66f0a38.js": {
       "bytes": 8994,
       "imports": []
     },
-    "web_modules/react.js": {
+    "build/web_modules/react.js": {
       "bytes": 215,
       "imports": [
         {
-          "path": "web_modules/common/index-e66f0a38.js"
+          "path": "build/web_modules/common/index-e66f0a38.js"
         },
         {
-          "path": "web_modules/common/index-e66f0a38.js"
+          "path": "build/web_modules/common/index-e66f0a38.js"
         }
       ]
     },
-    "web_modules/react-dom.js": {
+    "build/web_modules/react-dom.js": {

(the + version is 0.8.24, the other is 0.8.23).
snowpack adds the extraneous build/ prefix here

And so we end up with build/build.

I think it's a bug /cc @FredKSchott , snowpack should probably handle that case

[Monkatraz]

I can also say that this started happening to me. Thanks for figuring out it was the esbuild version, I went back a version and that resolved the problem.

[FredKSchott]

+1, thanks for debugging @pschyska. Issue created #2063 to find out what changed, hopefully just a small fix on our end. Will also start pinning to exact versions until esbuild reaches 1.0 to protect against this in the future