feat: add more fields into package.json

src/types/packagejson.ts

@@ -114,6 +114,10 @@ export interface PackageJson {
    * If your module is meant to be used client-side the browser field should be used instead of the main field. This is helpful to hint users that it might rely on primitives that aren’t available in Node.js modules. (e.g. window)
    */
   browser?: string | Record<string, string | false>;
+  /**
+   * The `unpkg` field is used to specify the URL to a UMD module for your package. This is used by default in the unpkg.com CDN service.
+   */
+  unpkg?: string;
   /**
    * A map of command name to local file name. On install, npm will symlink that file into `prefix/bin` for global installs, or `./node_modules/.bin/` for local installs.
    */
@@ -182,5 +186,31 @@ export interface PackageJson {
    * The optional engines field is used to specify the versions of npm and node that your stuff works on.
    */
   workspaces?: string[];
+  typesVersions?: Record<string, Record<string, string[]>>;
+  os?: string[];
+  cpu?: string[];
+  publishConfig?: {
+    registry: string;
+    tag: string;
+    access: "public" | "restricted";
+
+    // pnpm
+    executableFiles?: string[];
+    directory?: string;
+    linkDirectory?: boolean;
+  } & Pick<
+    PackageJson,
+    | "bin"
+    | "main"
+    | "exports"
+    | "types"
+    | "typings"
+    | "module"
+    | "browser"
+    | "unpkg"
+    | "typesVersions"
+    | "os"
+    | "cpu"
+  >;
   [key: string]: any;
 }