New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

types-package-json

Package Overview
Dependencies
Maintainers
1
Versions
28
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

types-package-json - npm Package Compare versions

Comparing version 0.0.1-0 to 0.0.10

10

package.json
{
"name": "types-package-json",
"version": "0.0.1-0",
"version": "0.0.10",
"license": "GPL-3.0",
"files": [
"dist"
],
"author": "Artur Kurowski <radarsu@gmail.com>",
"homepage": "https://github.com/radarsu/types-package-json#readme",
"main": "dist/index.js",
"types": "dist/index.d.ts",
"scripts": {},
"dependencies": {},
"devDependencies": {
"typescript": "^3.9.5",
"chalk": "^4.1.0"
"chalk": "^4.1.0",
"@radrat/cli": "0.0.15"
}
}

@@ -1,2 +0,2 @@

# Description
# types-package-json

@@ -9,2 +9,4 @@ A handful set of **package.json** types and interfaces to improve working with dynamically imported **package.json** files. **@types/package-json** became deprecated as **package.json** files imported by typescript come with it's own type definitions. Sometimes though, when you import files dynamically type becomes **any** and that's when this package becomes useful.

`npm i -D types-package-json`
```ts

@@ -14,3 +16,3 @@ import { IPackageJson } from 'types-package-json';

const packageJsonPath = path.resolve(process.cwd(), `package.json`);
const packageJson: IPackageJson = await import(packageJsonPath);
const packageJson: Partial<IPackageJson> = await import(packageJsonPath);
```

@@ -17,0 +19,0 @@

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc