-
Notifications
You must be signed in to change notification settings - Fork 363
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
Run webpack dashboard from .js file. #339
Comments
Could you provide a minimal sample repository showing what you’re trying / would want to work? |
So basically this is what I am trying (Not my actual setup, just a bare minimum to show the steps)
and then I have this file that handles the build process(Not using a cli because the actual file does much more than shown here)
And in my package.json, I execture my
This structure currently does not display anything inside the console. one possible approach would be to be able to pass a callback to DashboardPlugin that will return something that I can use to construct the dashboard in the console window. I was initially thinking |
I actually just realized that adding the following to my
// and then use the plugin with |
I have an example running the dashboard from a TS config webpack config file for this PR: #341 Just checkout the repository and run If you're still hitting an error, can you please open up a minimal repository with what you'd expect (or like) to work as an example, so I can install + build and see the failure myself? This makes it much easier to debug rather than guessing as to your setup... Thanks! |
Oh, reading this more -- the dashboard currently relies on inter-process communication between a webpack process and the dashboard (really a websocket server that pretty prints stuff). Maybe what you need is something like:
|
Is it possible to use this plugin if I am executing my webpack from non-cli environment? I run my webpack compiler from a .ts file without cli scripts and it seems like in those cases DashboardPlugin does not output any info.
The text was updated successfully, but these errors were encountered: