filenames.config.js can not be customized in project root

[marcoluzi]

Describe the bug

In your README.md, in the section customizing build paths it is statet, that the build paths and file names can be changed by placing a filenames.config.js in the project root. It seems like the toolkit is not checking if this file is available in the project root and requires its own default file. See here.

I suggest to implement a logic to check for a custom config file, like it is done with the config files for babel, stylelint, webpack etc.

Steps to Reproduce

1. Create filenames.config.js in the project root.
2. Change filenames.
3. Build the project.

Screenshots, screen recording, code snippet

No response

Environment information

No response

WordPress information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[nicholasio]

That's for the catch I don't know why it wasn't checking for that path... it's not something we used very often so likely why it was overlooked for so long.

[nicholasio]

Fixed in #355