Skip to content

Consider dropping node@6. #151

Description

@wtgtybhertgeghgtwtg

Mostly so micromatch can be bumped. micromatch@3 has some notable performance and size penalties but micromatch@4 requires node>=8. This'd probably close #143 and make #147 a little more straightforward. jest is also currently looking to drop node@6 support for the next major, so it'd need this to be done to fully feel the effects.

I'll file a PR if this is acceptable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions