Version
4.5.1
OS Version
macOS 14.5
Node.js Version
18.19.0
Link to minimal reproduction
https://github.com/yingpengsha/father-extends-config-plugin-not-work-issue
Steps to reproduce
modify .fatherrc like this:
import { defineConfig } from "father"
export default defineConfig({
cjs: {},
esm: {},
// ! using plugin directly, console will log 'plugin is running'
// plugins: ['./plugin.ts']
// ! not work
extends: './.father.forward.ts',
})
then run pnpm run build, you will not see the log:
info - [plugin: ./plugin.ts] plugin is running
What is expected?
father should load the config from extends path, and run the plugin.
the console should log:
info - [plugin: ./plugin.ts] plugin is running
What is actually happening?
when you use the extends configuration, the plugins configuration in the inherited configuration does not take effect
Any additional comments? (optional)
No response