Skip to content

Instantly share code, notes, and snippets.

@rauschma

rauschma/deploying_es6.md

Last active April 8, 2018 02:26
Show Gist options
  • Save rauschma/74665d9ab8635f402176 to your computer and use it in GitHub Desktop.
Save rauschma/74665d9ab8635f402176 to your computer and use it in GitHub Desktop.
Download ZIP
Options for deploying ES6 code
Raw
deploying_es6.md

This is a rough overview of the options for deploying ES6 to current JavaScript environments. Not everything can be combined with everything:

  • Decide on a transpiler (for your code):
    • TypeScript
    • Traceur
    • 6to5
  • Decide on a package manager (for existing libraries):
    • npm
    • Bower
    • jspm
  • Decide on a module system (for the complete app):
    • RequireJS
    • Browserify
    • webpack
    • SystemJS

Did I forget anything important (I want this list to be small, not exhaustive)?

@nzakas
Copy link

nzakas commented Feb 9, 2015

Decide on a linter.

@tjconcept
Copy link

Step 2 can be reduced to "npm".

@jaydson
Copy link

jaydson commented Feb 9, 2015

@nzakas ESLint is your choice? I mean, JSHint and JSCS(for code-style) are far from being (ES2015/ES6/ES2016/ES7)-compatible. Is ESLint ahead on this?
Actually i was forced to disable linting stuff in my ES6 projects, for example: JSRocksHQ/harmonic#103

@gabrieledarrigo
Copy link

What about test and testing framework that are ES6 capable?

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