Error when building website with snowpack 3.1.2

[felipeqq2]

After I updated to snowpack 3.1, I get the following error when building the website:

[@snowpack/plugin-optimize] Error: ENOENT: no such file or directory, open 'C:\Users\user\folder\proj\dist\_snowpack\optimize-manifest.json'

When I run snowpack dev the error is not thrown.

[colinaut]

Yep I've been getting this too randomly with an Eleventy site I'm building running Snowpack ^3.2.2. Usually it's with a png icon file. Only fix I've found is to delete the _site file and then rerun dev. It works for a while seems to handle the png fine and then breaks again.

[Bcdo]

I get the same error, but it does not stop the build. As far as I can tell, I find no errors with the actual build, except the missing optimize-manifest.json file.

I did not update snowpack, it for some reason just started to happen, and when I test an older version of my repo, it can still throw the same error.

[Kiina]

Similar issue. But even the verbose output isn't really helpful. It builds everything and then fails as soon as it starts optimize:

[15:30:26] [snowpack] ✔ write complete. [0.26s]
[15:30:26] [snowpack] ! optimizing build...
[15:30:26] [@snowpack/plugin-optimize] optimize() starting…
[15:30:26] [@snowpack/plugin-optimize] Error: ENOENT: no such file or directory, open '\build\_snowpack\optimize-manifest.json'

so it's impossible to find the file with the problem but I can't just remove the optimize plugin for obvious reasons...

I think dev doesn't throw this error since the dev server doesn't optimize.

[Bcdo]

The _snowpack folder does not get created. I guess it is a folder the plugin itself is trying to create, but failing? Not sure what the purpose of the folder is besides holding the optimize-manifest.json.

It has worked before for me, I might try some older snowpack versions and see it that helps. Or perhaps older plugin version.

[Bcdo]

Downgraded to snowpack version 3.0.10 and it works perfectly fine. The _snowpack gets created, and the optimize-manifest.json and env.js populates the folder. Not sure which version is the breaking one, but at least the plugin is doing what it is supposed to.

Edit: Just realised the original question mentioned the break after updating to 3.1

[Kiina]

Yeah, 3.0.13 works, 3.1.0-pre.5 and up not. 3.1.0-pre.1 to 5 just give unhandled promise rejections at the build stage so it's hard to triage down to the commit.