-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
chore: create package run (WIP) #1308
Conversation
@ematipico should I keep the new package as |
@rishabh3112 Please review the following output log for errors:
See complete report here. |
I don't know yet. I still have to understand how's the whole user flow. |
Why we need that package? What is use case? How it can be used stadalone? As I see it makes no sense to use this package without webpack-cli. Therefore, separate it into two packages makes no sense |
This was suggested by @ematipico to separate it from main package to reduce dependency of main package. For more context, you may look at #1261 and the PR where I implemented it. |
I think about it overall and shifting it to it's own package will not be helpful in reducing main package size. So, I am closing this PR. |
What kind of change does this PR introduce?
refactor, Moves executer to it's own package
Did you add tests for your changes?
Will be moving tests to the repo in this PR itself, for now there is a dummy test.
If relevant, did you update the documentation?
No, will write documentation for the package in this PR itself.
Summary
As suggested by Emanuele, I am moving the executer to it's seperate package.
Does this PR introduce a breaking change?
No
Other information
Tasks needed to be done here