-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Repo Structure - Modularizing and Consuming other Webpack Repos #301
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
Comments
There's an effort going on for renewing the analyse tool. Integration is going to be interesting. Maybe we could consume it as a dependency (React component) and push it within an Any thoughts @bartekus? |
@bebraw I definitely agree about keeping things modular and the way the current analyze tool is structure should allow the whole component to work as either part of a bigger set or as an individual SPA. |
@bartekus Awesome. Good design would make it possible to run it through Electron and so on. Actually wrapping the site within Electron would be feasible (not sure of the exact benefit unless we add some features), but still. 👍 |
@bebraw I think the benefit in and of itself would be to push the envelope further and further and to keep trying new ways of utilizing the power that webpack based development affords so that we continue to lead and advance the javascript community. |
@bebraw @webpack/documentation-team I'm going to close this for now and try to focus mainly on knocking out documentation tasks for the next month or so. Once we get further along with the actual content, I think we can then take more time to clean everything up. This issue has so many parts to it that I think we should instead create smaller more targeted issues and re-open it once more pieces are in place. Some notes in the meantime:
Benefits to these changes:
As mentioned above, I'm going to try to direct my attention towards finishing the last few UI issues and then try to start a move to knock out as many documentation issues as possible. If anyone wants to pick up something from the list above, please create a new more targeted issue or PR that we can knock out quickly. Hopefully we'll open this back up in a couple months and start banging away with less high priority docs issues and more time on our hands 👍 . |
Opening a discussion for how we can break parts of this repo out (as we were discussing with the components) and consume other repos like
webpack/media
.From #297:
@bebraw that's a good idea, I was thinking via a submodule but maybe sticking with npm for everything is simpler...
I'm also interested in what the team's plans are for the analyze tool. Ideally maybe we could have shared repo of components and utilities that this site, the analyze tool, and others all consume for a consistent interface?
Or maybe things like the voting app and analyze tool can be separate SPAs that this site consumes and displays under one of it's routes?
The text was updated successfully, but these errors were encountered: