Skip to content
This repository was archived by the owner on Dec 1, 2024. It is now read-only.
This repository was archived by the owner on Dec 1, 2024. It is now read-only.

Strategy for supporting node versions #470

Description

@ralphtheninja

I was going through the LTS schedule for node. And at time of writing it looks like:

image

Currently I'm a bit confused on what strategy we should pick. Updating .travis.yml etc feels a bit random to me atm. Therefore I'd like us to have a clear strategy on which versions we should support and test on.

Here are some alternatives:

EDIT: Poll locked.

screenshot from 2018-07-08 13-02-13

With "enough es6 features" I mean at least have support for destructuring (since we currently started using this for levelup@2.0.0)

cc @Level/owners

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions