Description of the Change

Gives developers the option to use a toolkit.config.js file at the root of their project for custom 10up-toolkit configuration. If present this will override any toolkit config within package.json.

Closes #187

Alternate Designs

I had thought about modifying the getPackage function, but the package build config depends on this function to retrieve other properties from package.json. Only getTenUpScriptsConfig is concerned with custom config.

Possible Drawbacks

Might be a little confusing for devs now having 3 different options for custom config. I think this would at least eliminate the need to provide the option for a custom filenames.config.js.

Verification Process

Followed the contributing guidelines and tested with the 10up-theme. Removed 10up-toolkit from package.json, placed the configuration along with new entries within a toolkit.config.js at the root of the project, and all assets were processed as they should have been when running npm start.

Note: Tests are failing due to hasProjectFileMock.mockReturnValue(true) within multiple tests. Honestly I'm not sure what the preferred fix would be here.

Checklist:

• I have read the CONTRIBUTING document.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests passed.

Changelog Entry

Credits

Props @