Skip to content
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

Adding to the webpack build chain #11

Closed
trst opened this Issue Sep 20, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@trst
Copy link

trst commented Sep 20, 2018

Would you consider offering the ability to add packages to augment the build process for a project? For example, say I needed postcss features for a particular site I'm developing, or image compression, it would be cool if the developer could npm install the requisite packages and have those update the Vapid's build process.

Perhaps, allow developers to create vapid specific packages that depend on useful node packages, a la what gatsby.js does.

@srobbin srobbin added the feature label Sep 24, 2018

@srobbin

This comment has been minimized.

Copy link
Contributor

srobbin commented Sep 24, 2018

@trst Sure, I'm interested to hear more about how you think it might work, and/or what would need to be changed.

@trst

This comment has been minimized.

Copy link
Author

trst commented Sep 25, 2018

What I think would be preferable for development would be to have someway to integrate different packages that augment the build setup, without having to manually add and configure them upstream. So, if my latest project would benefit from imagemin and a responsive image solution, I could add/develop a package that would hook in, something like npm install vapid-imagemin and have a corresponding config file to tweak the settings to my particular project.

My thought was to alleviate too much effort on your upstream part and allow each project to be customised based on its requirement. (e.g., not all projects require IE support, therefore, no reason to bake in certain cssnext plugins, and not every project requires responsive srcsets created on build and so on.)

@stale

This comment has been minimized.

Copy link

stale bot commented Dec 24, 2018

This issue has been automatically marked as stale after 90 days of inactivity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Dec 24, 2018

@stale stale bot closed this Dec 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.