Andrej Leitner
Andrej Leitner
Just an idea, would it make sense to expose (properly typed) `socket.io._readyState`? There should be 3 possible values: `'closed' | 'opening' | 'open'`.
There are `socket.request.headers`, `socket.conn.request.headers` and `socket.handshake.headers` all referencing the same thing, so this is just a suggestion for a clearer interface around request data. Socket.IO server version: `3.1.0` https://github.com/socketio/socket.io/blob/3.1.0/lib/socket.ts#L126 https://github.com/socketio/socket.io/blob/3.1.0/lib/socket.ts#L587-L589...
## What you are doing? I have migrations written in typescript. These compiled worked fine until CLI of version `6.1.0`. They don't after updating to version `6.4.1`. ```bash npx sequelize...
Originally filed on `ts-node`, but the problem seems to be related to `tsconfig-paths`, detailed info: https://github.com/TypeStrong/ts-node/issues/1732 This seems to be related: https://stackoverflow.com/questions/66329553/ts-node-requires-newrelic-js-instead-of-node-module
Is there a plan to release version 5 in the foreseeable future?
### Pre-Migration Checklist - [X] I've read the [Migration Guide](https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/migrating-to-v3.html). - [X] I've reviewed the upgrading notes and major version differences mentioned in [`UPGRADING.md`](https://github.com/aws/aws-sdk-js-v3/blob/main/UPGRADING.md). - [X] I've checked [AWS Forums](https://forums.aws.amazon.com)...
- `request` library is fully deprecated, see https://github.com/request/request/blob/master/README.md or https://github.com/request/request/issues/3142 - and already introduces vulnerability into projects via https://app.snyk.io/vuln/SNYK-JS-AJV-584908