-
Notifications
You must be signed in to change notification settings - Fork 10
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
bundle / build less development #355
Labels
alpha.0
CLI
enhancement
Improve something existing (e.g. no docs, new APIs, etc)
RFC
Proposal and changes to workflows, architecture, APIs, etc
v0.10.0
Milestone
Comments
thescientist13
added
enhancement
Improve something existing (e.g. no docs, new APIs, etc)
RFC
Proposal and changes to workflows, architecture, APIs, etc
CLI
labels
May 31, 2020
Could even push it farther with web packaging for production |
thescientist13
changed the title
bundle-less for development
bundle / build less for development
Jul 13, 2020
thescientist13
changed the title
bundle / build less for development
bundle / build less development
Jul 18, 2020
Started working on this, seeing this as a critical path forward on the project taking into consideration all the rest of the items in the Architectural Digest Project. Will demo some of my thoughts at our next weekly team meeting. |
This was referenced Sep 22, 2020
This was referenced Oct 19, 2020
This was referenced Nov 7, 2020
This was referenced Nov 8, 2020
Closed
5 tasks
5 tasks
Merged
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
alpha.0
CLI
enhancement
Improve something existing (e.g. no docs, new APIs, etc)
RFC
Proposal and changes to workflows, architecture, APIs, etc
v0.10.0
Type of Change
Summary
As part of explorations into #305, continued into #354, and inspired by projects like Vite, es-dev-server, and Snowpack, it would be of interest to investigate a way to move away from bundling by default for development. webpack could still be used for production builds maybe, or maybe even something that is more ESM friendly, like Rollup.
Details
This would definitely require a lot of new work, but in a ESM first world, there are so many advantages in that the entire site wouldn't need to be prebuilt / bundled, and transformations could just happen on the fly + on demand. Plus all syntax could just be standardized to use
import
for everything.Not opposed to coming up something of our own, maybe as its own package? Also, simplifying this and using something like Rollup may allow us to not have to rely on having to webpack-ify everything, and also free up a ton a
devDependencies
in the@greenwood/cli
package.Would allow us to explore usage of import-maps as a possible solution (bare imports and routing in general), ex.
Some more specific webpacky things that we use webpack for that would have to be redone:
The text was updated successfully, but these errors were encountered: