Skip to content

es6->es5 transpile #6

Description

@stagas

a few things to consider:

  • is it worth it? it'll introduce too many issues, for stuff that will eventually be supported natively in the browsers
  • in-browser transpile will generate too much garbage, might be killing the live performance, maybe have a backend service and post es6 code, get es5 back?
  • we already have code with es6 style import/export so maybe a regex replace solution to commonjs require/exports?
  • this needs to be addressed before import modules #5

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions