[suggestion] throws an error when it doesn't find the file/path

[tassioFront]

[suggestion] throws an error when it doesn't find the file

I have been using the vite-plugin-static-copy for a while and recently I needed to move the file path it copies. So, I changed the copied file from src/old-path to src/new-path, but I forgot to update the plugin configuration:

  viteStaticCopy({
     targets: [
       {
         src: './src/old-path.js', // I must update this line, but even without doing it the build keeps working.
         //...more config
       },
     ],
   }),

Unfortunately, it does not throw any error, so I noticed it fails after manual validations. Does make sense to throw an error when the plugin doesn't find the file?

[sapphi-red]

I think we can have a warning log in build.

[tassioFront]

To be honest, I think it should fail once the application won't work as expected, but a warning would help a lot. 🙌

[tassioFront]

@sapphi-red, I was creating the PR when I saw this on my terminal:

This validation is done here

Guess it proves the warning is not enough. 😅 Anyway, let me know if makes sense to open the PR with an error msg; or I can keep the warning, but change the message like:

'No file was found to copy on ${src} src.'

otherwise, we can close the issue.

[tassioFront]

@sapphi-red what do you think?

[sapphi-red]

Hmmm, yeah, probably an error is better.
But I think throwing an error will break usecases like slidev (#52).

So I think we need to cut a major version and also add an option to ignore the error.

[tassioFront]

@sapphi-red perfect!

Let me know what you think about this changes.

[vedranstipancic]

This seriously hindered the way we use the plugin.
We have a common vite config for several projects. It includes some things to copy which are optional on projects. Until now it wasn't an issue, because it just didn't copy things it didn't find.
Now it

• breaks my build if nothing found
• if I turn on silent absolutely nothing gets copied, because one of the copies failed
• if I break up one copy into several copies, it doesn't work during development

It feels like we'd need the silent option on each target.

[tassioFront]

@vedranstipancic, which version were you using before it started, and which one now?