-
Notifications
You must be signed in to change notification settings - Fork 20
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
1.0.0 Roadmap #23
Comments
hey, do you have ETA? :) or how close are you? |
@Kepro Sorry 😢 |
@kotarella1110 do you need any help or smth? |
I need the following help.
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test it out:
Removed webpack packages from deps
This plugin depends on the plugin's own webpack, but it will be modified to depend on the webpack you installed.
Therefore, removed webpack packages (
webpack
,webpack-cli
,webpack-dev-server
) from deps ofpackage.json
and add the webpack packages to peerDeps (2b86b41).You need to install the webpack packages yourself before installing this plugin.
Add a new
--webpack
optionThis plugin has no way to map parameters sent to the CLI to a corresponding parameter in the webpack configuration file such as webpack-cli and webpack-dev-server.
Add a new
--webpack
option to make this possible.--webpack
option's parameters is passed to webpack-cli options or webpack-dev-server options.The
--webpackConfig
option will be removed in v1 by adding a new--webpack
option.Use
--webpack.config
option instead of--webpackConfig
option.Support various webpack configuration types
This plugin only supports exporting a single configuration object.
Covers other needs besides exporting a single configuration object.
Related Issues:
The text was updated successfully, but these errors were encountered: