Nuxt.js: Allow excluding files from the static folder on .nuxtignore

[jaireina]

What problem does this feature solve?

There are several cases where we need to include some test assets in the static folder so we can do development or run a mock version of an app. However those files are not needed for production, but they are bundled with everything within the static folder.
If we have a local folder inside of static where we put all of our test assets it would be great to have a way to tell webpack or the nuxt framework to ignore that local folder when we execute npm run build.

What does the proposed changes look like?

In .nuxtignore I should be able to include something like
static/local

In order to exclude the local folder from the final build.

_{This feature request is available on Nuxt community (#c9785)}

[Atinux]

I like this feature request, cc @clarkdo

[drewbaker]

I want this!

[clarkdo]

Sorry that I must have missed this request, I’ll look into it this week.

[erik06]

I'm looking for this exact feature. I put a json file in /static that I use during development that spoofs the authenticated user for testing and local development, but I don't want it to be included in the build. I would REALLY benefit from this feature, any progress?

[clarkdo]

@erik06 Sorry that I haven’t got any time to look into this, I’ll add this to my todos and prepare a pr ASAP.

[clarkdo]

@jaireina @erik06 .nuxtignore is a config file in src, so it's only loaded in building phase rather than server running. As files under static folder are isolated so they won't be bundled in to bundles files, so if you don't copy the files to production or remove them when you start server, it should work as expected.

[erik06]

@jaireina @erik06 .nuxtignore is a config file in src, so it's only loaded in building phase rather than server running. As files under static folder are isolated so they won't be bundled in to bundles files, so if you don't copy the files to production or remove them when you start server, it should work as expected.

I understand, It’s the manual removing/ignoring part that I’m hoping the ignore file will do for me. I’m aware that I can just remove my file that I don’t want, but it’s very manual, prone to forgetfulness and or dependent on another script to remove it when the site is built for production. I’m looking forward to your PR and very much appreciate your time spent on this!