Skip to content

Conversation

@brettz9
Copy link
Member

@brettz9 brettz9 commented May 13, 2019

  • Breaking change: Require Node 8
  • Refactoring: Use ES6 classes
  • Travis: Use Node 10, 12, 14
  • Linting: Add eslint-config-ash-nazg and apply (and remove jshint) to JS, Markdown, HTML
  • Maintenance: Add .editorconfig
  • Testing: Add nyc for coverage
  • Docs (README): Clean-up
  • npm: Add separate mocha (no-coverage) test script and add coverage to test
  • npm: Add package-lock.json
  • npm: Add recommended fields (contributors, homepage)
  • npm: Change deprecated licenses with license
  • npm: Add lint and lintfix scripts
  • npm: Update link from http to https
  • npm: Simplify test (full relative binary path not needed in npm scripts)
  • npm: Update devDeps.

Add changes similar to those proposed for passport (its depender)

@coveralls
Copy link

coveralls commented May 13, 2019

Pull Request Test Coverage Report for Build 33

  • 2 of 2 (100.0%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 10: 0.0%
Covered Lines: 5
Relevant Lines: 5

💛 - Coveralls

@adamhathcock adamhathcock requested a review from rwky May 13, 2019 07:06
@adamhathcock
Copy link

I need to get on the ball and add Typescript definitions now :)

@brettz9
Copy link
Member Author

brettz9 commented May 13, 2019

Cool :) I am trying to finish up a Promise PR if that may affect your plans...

And if we're pulling off the Band-Aid with a new Promises API anyways, I would also like to propose a new API so that function signatures or return objects like ret, user could be done as {ret, user} instead to allow for passing arguments and destructuring without needing to care about argument order.

@adamhathcock
Copy link

I’m happy to wait for Promises. I think optional paeans should be grouped into an object too.

@rwky
Copy link

rwky commented May 13, 2019

I'll check this once passport-next/passport#19 is merged.

@rwky rwky self-assigned this May 13, 2019
@brettz9 brettz9 force-pushed the linting branch 5 times, most recently from 8171ace to c398d71 Compare July 13, 2019 04:45
@brettz9 brettz9 force-pushed the linting branch 3 times, most recently from 2aa4020 to 8f14b99 Compare July 18, 2019 03:15
@brettz9
Copy link
Member Author

brettz9 commented Sep 13, 2019

I've updated the devDeps and linted/tested against these updates... As the single dependency of passport, I'd think this would be good to update to a new major version first so the next passport update could depend on it.

@brettz9
Copy link
Member Author

brettz9 commented Sep 13, 2019

But note that even with this PR, passport-strategy still has make files (as does passport-local)...

- Refactoring: Use ES6 classes
- Travis: Add Node 11 and 12
- Linting: Add eslint-config-ash-nazg (and remove jshint) to JS, Markdown, HTML
- Maintenance: Add `.editorconfig`
- npm: Add `package-lock.json`
- npm: Add recommended fields (contributors, homepage)
- npm: Change deprecated `licenses` with `license`
- npm: Add `lint` and `lintfix` scripts
- npm: Update link from http to https
- npm: Update chai, mocha
- npm: Simplify test (full relative binary path not needed in npm scripts)
- npm: Update devDeps.
- npm: Bump engines and browserslist to Node 10
- npm: Add separate `mocha` (no-coverage) test script and add coverage to `test`
@brettz9 brettz9 force-pushed the linting branch 2 times, most recently from cd0bdfd to 00d1f14 Compare February 17, 2021 03:08
…plugin-markdown` and `eslint-plugin-jsdoc`

- npm: Update devDeps.
brettz9 added 2 commits July 1, 2021 09:07
- npm: Update devDeps.
- Testing: Avoid need for own bootstrap file
- Testing Check Node 16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants