Skip to content

esnext to es2018 #279

Open
Open
@imcotton

Description

@imcotton

Given both TypeScript and ClosureCompiler have fixed es2018 targeting, good to lock down es2018 instead of esnext?

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