Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Proposal for 3.0.0
See original GitHub issueWe have a few breaking changes that are getting backed up, and I think it would be nice to publish them and put out 3.0.0. We won’t get much in the way of new functionality, but I think it will solve some problems for people. So, I’d like to propose the following for a 3.0.0 release in the next few weeks:
- Drop support for Node.js < 4 (LTS version) (https://github.com/eslint/eslint/issues/4483)
- Update
eslint:recommended(with whatever is appropriate) (https://github.com/eslint/eslint/issues/6403) - Set a default value for
complexity(https://github.com/eslint/eslint/issues/6021) - Output error if no config file is found (https://github.com/eslint/eslint/issues/5987)
-
Use XDG basedirs for personal config file (https://github.com/eslint/eslint/issues/6008) - Suppress ignored file warnings in
executeOnText()(https://github.com/eslint/eslint/issues/6302) - Simplify eslint process exit code (https://github.com/eslint/eslint/issues/6368)
A lot of these are fairly simple changes that could have positive impacts on end users, so maybe we can swarm and get these done?
Thoughts?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:19
- Comments:26 (23 by maintainers)
Top Results From Across the Web
proposal - npm
Takes a node-style callbacking function and converts it into a Promise automagically. Latest version: 3.0.0, last published: 7 years ago.
Read more >ProposalEvaluator (Jadex Active Component Platform 3.0.0-RC32 ...
A default implementation of the proposal evaluator interface. The implementation determines acceptable proposals by comparing proposals or evaluations to a ...
Read more >Agency Proposal 3.0, Graphic Templates - Envato Elements
Description ### BigBrand Proposal: Win the job with this beautiful premium 24 page template. It contains Quote Signoff / Timeline / Budget /...
Read more >1 Introduction 2 Text Proposal - 3GPP
In WG1 #8 in New York, the proposal of changing the current initial offset value of rate ... Proposed change affects: ... 3G...
Read more >Kafka Improvement Proposals - Apache Software Foundation
This page describes a proposed Kafka Improvement Proposal (KIP) process for ... KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Let’s table the converting to ES6 discussion for now (if someone wants to open up a separate issue to discuss, please do, but that will come after 3.0.0 and so isn’t relevant to planning).
And please, let’s not add any more issues to my original description unless we all agree first. Otherwise, the reactions on that description and the comments are a bit misleading.
Part of the rationale for doing 3.0.0 in this lightweight way is to avoid the breaking feature explosion we’ve tended to have with previous major release (where everyone wants to get in “just one more” breaking change). That’s also meant the nightmare of doing alpha and beta releases, which I definitely would like to avoid going forward.
I’d say at this point the only thing we should do is remove issues from the list and not add them. With what we have, I think we can shoot for 3.0.0 next Friday. Sound reasonable?
@ilyavolodin I will post there soon. I just haven’t had the time to write up a convincing argument recently.