Skip to content

hiherto-elements/es-next-modules

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

JS Development without Babel <3

Build Status

  1. Use a typescript environment that can interpret es6 modules
  • Hello deno
  • do all the dev and test work there. As it is a platform that supports 100% es6 syntax
  1. Write modern javascript
  • just dont think about require
  • have no code relevant package.json
  • although I like the automation with npm scripts and lerna
  1. Write an adapter to node-js
  • integration test
  • ship to npm
  • Boom: Result consumable in node/browser and the console

Setup

Why do things this way

  1. Babel config is hell.
  • a bit like perl - 50 ways to get things done
  • dependency hell for just interpreting es-next code
  1. Babel is fine, just not for development
  2. Managing node_modules is a bit over the top
  • not for development
  • use node_modules only for dependencies not development deps

Releases

No releases published

Packages

No packages published

Languages