3 ms·

Here's the changes between the last 13.x tag and the latest (at the moment) 14.x tag (14.0.2): https://github.com/standard/standard/compare/v13.1.0...v14.0.2 ht

Here's the changes between the last 13.x tag and the latest (at the moment) 14.x tag (14.0.2): https://github.com/standard/standard/compare/v13.1.0...v14.0.2 https://github.com/standard/standard/compare/v13.1.0...v14.0... Analyzing the changes I leave as an exercise to the reader. Regardless of the effort etc. and whether or not these changes were primarily functional or related to marketing, I personally support FOS maintainers doing whatever they want with the software they offer for free. It would be trivial to make a fork of Standard without the adware if you wanted, and the MIT license explicitly allows it. So more power to feross for his free offerings! And complainers: put your fork where your mouth is.

hobofan 7y ago
For a more complete look at the changes, this should also include the diffs of the project-internal dependencies that were bumped. https://github.com/standard/eslint-config-standard/compare/v13.0.1...v14.0.1 https://github.com/standard/eslint-config-standard/compare/v... https://github.com/standard/eslint-config-standard-jsx/compare/v7.0.0...v8.0.1 https://github.com/standard/eslint-config-standard-jsx/compa... https://github.com/standard/standard-engine/compare/v11.0.1...v12.0.0 https://github.com/standard/standard-engine/compare/v11.0.1....
- duncan-donuts 7y ago
  This honestly makes it worse. I'm not even sure how you could call this stuff major version bumps.
  - csande17 7y ago
    The main repo has a testing script to make sure changes that cause previously-passing code to fail lint checks only happen in new major versions. Like SemVer, but for linter configuration files. This would be an admirable commitment to stability if the project wasn't on its fourteenth major version.
wolfd 7y ago
While a lot of commits, the actual content shows very few functional changes. Actually, most of the changes are indeed ads for companies that use the package.
m712 7y ago
It just seems like they changed documentation and moved some ES5 constructs to ES6, there isn't even a behavior change in those commits. Is this what took 40 hours to update? Why is this worth a major version bump?

hobofan 7y ago

For a more complete look at the changes, this should also include the diffs of the project-internal dependencies that were bumped. https://github.com/standard/eslint-config-standard/compare/v13.0.1...v14.0.1 https://github.com/standard/eslint-config-standard/compare/v... https://github.com/standard/eslint-config-standard-jsx/compare/v7.0.0...v8.0.1 https://github.com/standard/eslint-config-standard-jsx/compa... https://github.com/standard/standard-engine/compare/v11.0.1...v12.0.0 https://github.com/standard/standard-engine/compare/v11.0.1....

duncan-donuts 7y ago
This honestly makes it worse. I'm not even sure how you could call this stuff major version bumps.
- csande17 7y ago
  The main repo has a testing script to make sure changes that cause previously-passing code to fail lint checks only happen in new major versions. Like SemVer, but for linter configuration files. This would be an admirable commitment to stability if the project wasn't on its fourteenth major version.

wolfd 7y ago

While a lot of commits, the actual content shows very few functional changes. Actually, most of the changes are indeed ads for companies that use the package.

m712 7y ago

It just seems like they changed documentation and moved some ES5 constructs to ES6, there isn't even a behavior change in those commits. Is this what took 40 hours to update? Why is this worth a major version bump?