> It seems to me that this is nearly universal among nontrivial front and projects. Each one, through its build configuration, has a slightly different subset o

> It seems to me that this is nearly universal among nontrivial front and projects. Each one, through its build configuration, has a slightly different subset of all the language features supported by the current crop of JavaScript derived languages. It don't know what you mean, but it's certainly avoidable. You can do a few things: * Only use language features of the browsers you are targeting. If you are targeting evergreen browsers (not IE) you can use most of ES2015 including classes, arrow functions, and template literals. * Or use a transpiler but stick to some sane judgment of presets, preferable Stage 3 or greater, but at least stuff that's on the standards track. * Don't use stuff like this: https://www.npmjs.com/package/babel-root-import https://www.npmjs.com/package/babel-root-import that exists only to save yourself a couple of keystrokes.