You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
querystring@0.2.1 dev
node_modules/@serverless/platform-client/node_modules/querystring
querystring@"^0.2.1" from @serverless/platform-client@4.5.1
node_modules/@serverless/platform-client
@serverless/platform-client@"^4.3.2" from @serverless/dashboard-plugin@6.2.2
node_modules/@serverless/dashboard-plugin
@serverless/dashboard-plugin@"^6.2.2" from serverless@3.24.1
node_modules/serverless
dev serverless@"^3.24.1" from the root project
peer serverless@"2 || 3" from serverless-plugin-typescript@2.1.4
node_modules/serverless-plugin-typescript
dev serverless-plugin-typescript@"^2.1.2" from the root project
@serverless/platform-client@"^4.3.2" from serverless@3.24.1
node_modules/serverless
dev serverless@"^3.24.1" from the root project
peer serverless@"2 || 3" from serverless-plugin-typescript@2.1.4
node_modules/serverless-plugin-typescript
dev serverless-plugin-typescript@"^2.1.2" from the root project
Proposed solution (optional)
The official recommendation is to replace querystring functionality with URLSearchParams. Unless there are already plans doing so, the possibility of contributing to @serverless/platform-client would create potential pull requests addressing the matter.
The text was updated successfully, but these errors were encountered:
As far as I can see no steps have been taken yet. @serverless/platform-client is not a public repository and its code is currently only visible in the NPM registry.
Is there an existing issue for this?
Use case description
npm audit
reports the usage of the deprecated querystring package within @serverless/platform-client:Proposed solution (optional)
The official recommendation is to replace
querystring
functionality withURLSearchParams
. Unless there are already plans doing so, the possibility of contributing to@serverless/platform-client
would create potential pull requests addressing the matter.The text was updated successfully, but these errors were encountered: