Skip to content

Instantly share code, notes, and snippets.

@stereobooster

stereobooster/Should I make webpack or babel plugin for X.md

Created May 10, 2018 18:06
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save stereobooster/b7cfcffd043d9f2c02c343bb41f18f26 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save stereobooster/b7cfcffd043d9f2c02c343bb41f18f26 to your computer and use it in GitHub Desktop.
Download ZIP
Should I make webpack or babel plugin for X?
Raw
Should I make webpack or babel plugin for X.md

Should I make webpack or babel plugin for X?

Can X be implemented as standalone command line application?

If yes, chose a standalone application over the webpack plugin.

Examples:

Can X be implemented as babel-plugin-macros?

If yes, chose a babel-plugin-macros over the webpack plugin or other type of babel plugin.

Why

The webpack plugin or babel plugin, except macros, will require touching webpack config or .babelrc, which is problematic and consumes a lot of developers time unnecessarily. I saw at least twice fresh project started by the whole team choosing "ideal" webpack setup.

Autocomplete reduces typing required by about 25%. On Google, that’s over 200 years of typing time per day.https://t.co/W2aPeedsbj

— Luke Wroblewski (@lukew) April 23, 2018

All time saved by Google autocomplete is spent to configure webpack. This is not an attack on webpack. I like webpack, I use webpack, I'm grateful for webpack. It is we, developers, who create problems ourselves by creating plugins, which requires attention, without real need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment