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
This is about packages pulled in by using Quicktype
Context (Environment, Version, Language)
This is about output from npm install
CLI, npm, or app.quicktype.io: npm install
Version: 23.0.170
Description
When running npm install I get this output
$ npm install
npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
The warnings are due to a dependency on @mark.probst/[email protected]:
Failing any attention from the typescript-json-schema package maintainer, there is another package that might be of interest...? Maybe? I only know about that because of a link in the typescript-json-schema repository:
Issue Type
This is about packages pulled in by using Quicktype
Context (Environment, Version, Language)
This is about output from
npm install
CLI, npm, or app.quicktype.io:
npm install
Version: 23.0.170
Description
When running
npm install
I get this outputThe warnings are due to a dependency on
@mark.probst/[email protected]
:Input Data
A dependency in
npm
package.json
Expected Behaviour / Output
There should be zero warnings or errors from npm
Current Behaviour / Output
See above
Steps to Reproduce
As noted above, create a project, depend on Quicktype, and run
npm install
Possible Solution
Two issues exist against the offending package:
Failing any attention from the typescript-json-schema package maintainer, there is another package that might be of interest...? Maybe? I only know about that because of a link in the typescript-json-schema repository:
https://github.com/vega/ts-json-schema-generator
The text was updated successfully, but these errors were encountered: