Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cumulative (including other forks) enhancements proposal #45

Closed
wants to merge 5 commits into from

Conversation

ddimitrioglo
Copy link
Contributor

@ddimitrioglo ddimitrioglo commented Jan 8, 2024

🀝 @shahyar 's changes have been taken (PR: #37) as a basement.

βœ… On top of them, the following have been added:

  • Used @typescript-eslint/recommended rules (vs custom set)
  • Removed eslint-plugin-jsdoc, eslint-plugin-mocha, eslint-plugin-no-null
  • Moved tests into test directory (src is not "polluted", it's easier to prepare build, etc.) [opinionated but inspired by Angular 😁]
  • Fixed 15 vulnerability notifications
  • Update engines.node from v14 to v18 + reflect in ci/cd and local development (.nvmrc)
  • Moved graphql-subscriptions to peer-dependencies
  • Replaced mocha, chai, chai-as-promised, nyc, sinon and sinon-chai with jest as a standalone testing solution
  • Introduced swc (Rust-based compiler) which works well with jest
  • Improved release flow (reduce npm tarball Unpacked Size from 44.4 kB to 22 kB by removing unnecessary files)

⚠️ Check needed by maintainers:
Could not test "publishPath": "/lib" option of release-it (don't have permissions), please --dry-run to check if lib directory is the only one that is going to be published as an npm package.

shahyar and others added 5 commits January 8, 2024 11:55
- Breaking: Minimum Node.js version >=14
- Breaking: `graphql-subscriptions` >= 2.0.0
- Breaking: `graphql` 16.x; dropped support for 14.x 15.x
- Changed from deprecated `tslint` to `eslint`
- Upgraded vulnerable packages `nodemon`, `mocha`, `sinon`, `ts-node`
@chdanielmueller
Copy link
Member

Merged with #46

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.

3 participants