-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin: Introduce tools
folder with configuration files
#33281
Conversation
Size Change: 0 B Total Size: 1.06 MB ℹ️ View Unchanged
|
205575d
to
e7c1034
Compare
|
||
return `./build/[name]/index.min.js`; | ||
}, | ||
path: join( __dirname, '..', '..' ), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only code change in comparison to the original webpack.config.js
file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good, I do wonder whether "tools" is the right name though, it feels this is more "config" than "tools", though both are problematic in some ways:
- tools: what about documentation tool, release tool, api doc tool...
- config: what about the other configs we have spread everywhere :)
I followed the pattern that is used in https://github.com/WordPress/wordpress-develop/tree/master/tools |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, I'm just nitpicking above. I like that it aligns with core and potentially simplify porting updates to the configs.
Description
This PR proposes a new top-level folder with configuration files for tools:
It allows two things:
test/linter
folder totools/eslint
tools/webpack/packages
The next step would be to split webpack config into two subconfigs:
It's similar to what's proposed in WordPress core in WordPress/wordpress-develop#1412.