feat: support cjs extension for config #873
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using Maizzle in a project with "type": "module", the configuration file
config.js
is treated like an ESM module, which causes an error (since it's written in CommonJS). To fix this, it should be renamed toconfig.cjs
, but it doesn't seem like Maizzle supports this just yet (since it relies on Node's auto-extension resolution algorithm, which doesn't work for the.cjs
extension).This PR just adds some explicit checks for
.cjs
files in the configuration loader so that Maizzle correctly loads configuration files that end with a.cjs
extension.Let me know if you have any questions!