{"_id":"ts-expose-internals-conditionally","_rev":"14-3be6724c5e018a06c5f259a3a73be5ec","name":"ts-expose-internals-conditionally","dist-tags":{"latest":"1.0.0-empty.0","beta":"5.2.0-beta","rc":"5.3.1-rc"},"versions":{"5.0.2":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.0.2","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.0.2","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-7XaIyj0vap6mXgyN6xJ4DM77z4SkoqmI6Gr0sKAGQozjHNYuIVKqrnlPFR18ViiAI5XESFPvS49Uh7EeSX16SA==","shasum":"53f420aaded255712dac4972e12bd3f1e06cc628","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.0.2.tgz","fileCount":5,"unpackedSize":1235481,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBO8Aj6S1AVCDoLwKztMOPOmSdN6p3tFtoeNQ/llhVdxAiB9Y0lDEoz4THuk0pJohgrIUUp5wb6RMIPJFJ7m2j+Hgg=="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.0.2_1703114245113_0.8664183301397541"},"_hasShrinkwrap":false},"5.0.3":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.0.3","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.0.3","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-cES37f23QGzXN0mkt02P6caY7YbuKMS8lASNIAguiIJWukBmw4u9+yRvmybJTljm1aWWRQY0GOdFjM5zJopzKA==","shasum":"df4f3515f90f30ba1c3562eaf14e038a673554e8","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.0.3.tgz","fileCount":5,"unpackedSize":1235481,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEEYOpbljUcSfH2r0K0xyw6NyRRKBD93UGMHo8QG/ZVKAiEA9XYwo8fYlt8nfSq75Ixmppwv3Bu6W3bMBmG/d0TpC5Q="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.0.3_1703114293147_0.18566106116868508"},"_hasShrinkwrap":false},"5.0.4":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.0.4","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.0.4","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-7EDdcWtXTfh8bfCLE5Exe4c0+LzKBa/JUzZNVwh2Q7HC2Dor9RF9tsgXneOSB8wQb5zuj10BjzPWXg+ew8RJcQ==","shasum":"7e5b9b46757caf5394a9f83a217c5fb7f9933fec","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.0.4.tgz","fileCount":5,"unpackedSize":1235582,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDi2yW9j8NmsRnfcxVkcW+D5f/PMvxyed0p5/XCcA543gIhANlxAu5bLM96iLeAAKSbTwxK0Ho/vb5wVvnMX+v7YxXY"}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.0.4_1703114343100_0.9377990458524281"},"_hasShrinkwrap":false},"5.1.0-beta":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.1.0-beta","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.1.0-beta","readme":"# ⚠️ Do not use this unless you understand the risks ⚠️\n\nYou’re probably better off using [ts-expose-internals](https://github.com/nonara/ts-expose-internals) directly.\n\n# ts-expose-internals-conditionally\n\nA simple fork of the excellent [ts-expose-internals](https://github.com/nonara/ts-expose-internals), but only activates when compiled with:\n\n```json5\n// tsconfig.json\n{\n  \"compilerOptions\": {\n    \"module\": \"nodenext\", // or \"node16\" or \"bundler\" - must support package.json \"exports\"\n    \"customConditions\": [\"ts-expose-internals\"]\n  }\n}\n```\n\n## Why?\n\nIf you are publishing a library that uses ts-expose-internals in its implementation, and exposes some of TypeScript’s _non-internal_ types in its API, your own declaration files will end up referencing ts-expose-internals:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals\" />\n\nimport { CompilerOptions } from \"typescript\";\nexport function doSomethingWrappingTypeScript(\n  fileName: string,\n  typeScriptOptions: CompilerOptions\n): unknown;\n```\n\nEven though `CompilerOptions` is part of TypeScript’s public API, ts-expose-internals is a module augmentation that re-declares and augments everything in the `typescript` module. So when `tsc --declaration` notices that the `CompilerOptions` you’re referencing in your own compilation is declared in `\"typescript\"` but augmented in `\"ts-expose-internals\"`, it adds an explicit reference to `\"ts-expose-internals\"` to make sure everyone using your library sees the same `CompilerOptions` that you do.\n\nNormally, this is a very desirable behavior. Without it, users could end up with types in their `node_modules` that reference things that don’t exist in their own compilation, leading to errors. But in the case of ts-expose-internals, you probably _don’t_ want to expose all of TypeScript’s internals for all of your users. You want the internals when compiling your own implementation code, but your public API can be consumed without them.\n\nBy using `ts-expose-internals-conditionally` and compiling with `\"customConditions\": [\"ts-expose-internals\"]` in your tsconfig.json, your compilation will include the ts-expose-internals module augmentation, but your users’ compilations won’t (assuming they don’t also have `\"customConditions\": [\"ts-expose-internals\"]`).\n\nOf course, this is **not safe**, because if you accidentally reference anything internal that makes it into your declaration files, your users will get errors:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals-conditionally\" />\n//  ^ references an empty file for users!\n\nimport { ModeAwareCache } from \"typescript\";\n//       ^^^^^^^^^^^^^^\n// Module \"typescript\" has no exported member 'ModeAwareCache'.\n```\n\nTo be safe, you should re-check your output declaration files _without_ any `customConditions` to ensure they’re portable.\n\n## This must go in `dependencies`, not `devDependencies`\n\nSince `tsc --declaration` will emit a reference to `\"ts-expose-internals-conditionally\"` in your declaration files, you need to ensure that reference actually resolves (to an empty file) for your users, which means they will need this package installed, which means it should go in your `dependencies`, not your `devDependencies`.\n\n## Why is this a fork and not an intermediate dependency?\n\nI thought I would get away with making a package with two tiny files:\n\n```ts\n// index.d.ts\n/// <reference types=\"ts-expose-internals\" />\n```\n\n```ts\n// empty.d.ts\n```\n\nBut it turns out that `tsc --declaration` still emits a reference directly to `\"ts-expose-internals\"`, even when it’s referenced transitively through this proxy package. This behavior actually makes sense, so I don’t think there was a way to do this without publishing an independent package.\n","readmeFilename":"README.md","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-QN39aYe0ADU8a2iYnXgXCsrZmeVgvtTpZV1TBEuZll35P+MlyG8h+NwjuhRKYa5B3fWpz52SyRvnxZaDbu71iQ==","shasum":"5e4cfd8da68688e0dea52a20a6350929b89f8f37","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.1.0-beta.tgz","fileCount":5,"unpackedSize":1240723,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBPWRayzB+XZL/2LU9ufT/RVqzVeJ0+uqIeLpQFjywk9AiEAvykplPiaaSqpCR8Yo4hYA+e26HUv9S8FaZV5qmQNbQY="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.1.0-beta_1703114391700_0.8733583617835676"},"_hasShrinkwrap":false},"5.1.1-rc":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.1.1-rc","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.1.1-rc","readme":"# ⚠️ Do not use this unless you understand the risks ⚠️\n\nYou’re probably better off using [ts-expose-internals](https://github.com/nonara/ts-expose-internals) directly.\n\n# ts-expose-internals-conditionally\n\nA simple fork of the excellent [ts-expose-internals](https://github.com/nonara/ts-expose-internals), but only activates when compiled with:\n\n```json5\n// tsconfig.json\n{\n  \"compilerOptions\": {\n    \"module\": \"nodenext\", // or \"node16\" or \"bundler\" - must support package.json \"exports\"\n    \"customConditions\": [\"ts-expose-internals\"]\n  }\n}\n```\n\n## Why?\n\nIf you are publishing a library that uses ts-expose-internals in its implementation, and exposes some of TypeScript’s _non-internal_ types in its API, your own declaration files will end up referencing ts-expose-internals:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals\" />\n\nimport { CompilerOptions } from \"typescript\";\nexport function doSomethingWrappingTypeScript(\n  fileName: string,\n  typeScriptOptions: CompilerOptions\n): unknown;\n```\n\nEven though `CompilerOptions` is part of TypeScript’s public API, ts-expose-internals is a module augmentation that re-declares and augments everything in the `typescript` module. So when `tsc --declaration` notices that the `CompilerOptions` you’re referencing in your own compilation is declared in `\"typescript\"` but augmented in `\"ts-expose-internals\"`, it adds an explicit reference to `\"ts-expose-internals\"` to make sure everyone using your library sees the same `CompilerOptions` that you do.\n\nNormally, this is a very desirable behavior. Without it, users could end up with types in their `node_modules` that reference things that don’t exist in their own compilation, leading to errors. But in the case of ts-expose-internals, you probably _don’t_ want to expose all of TypeScript’s internals for all of your users. You want the internals when compiling your own implementation code, but your public API can be consumed without them.\n\nBy using `ts-expose-internals-conditionally` and compiling with `\"customConditions\": [\"ts-expose-internals\"]` in your tsconfig.json, your compilation will include the ts-expose-internals module augmentation, but your users’ compilations won’t (assuming they don’t also have `\"customConditions\": [\"ts-expose-internals\"]`).\n\nOf course, this is **not safe**, because if you accidentally reference anything internal that makes it into your declaration files, your users will get errors:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals-conditionally\" />\n//  ^ references an empty file for users!\n\nimport { ModeAwareCache } from \"typescript\";\n//       ^^^^^^^^^^^^^^\n// Module \"typescript\" has no exported member 'ModeAwareCache'.\n```\n\nTo be safe, you should re-check your output declaration files _without_ any `customConditions` to ensure they’re portable.\n\n## This must go in `dependencies`, not `devDependencies`\n\nSince `tsc --declaration` will emit a reference to `\"ts-expose-internals-conditionally\"` in your declaration files, you need to ensure that reference actually resolves (to an empty file) for your users, which means they will need this package installed, which means it should go in your `dependencies`, not your `devDependencies`.\n\n## Why is this a fork and not an intermediate dependency?\n\nI thought I would get away with making a package with two tiny files:\n\n```ts\n// index.d.ts\n/// <reference types=\"ts-expose-internals\" />\n```\n\n```ts\n// empty.d.ts\n```\n\nBut it turns out that `tsc --declaration` still emits a reference directly to `\"ts-expose-internals\"`, even when it’s referenced transitively through this proxy package. This behavior actually makes sense, so I don’t think there was a way to do this without publishing an independent package.\n","readmeFilename":"README.md","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-rUde2SFOq1qcNIQpacBGA/66xH7Hpb97iqe4v/k18lqRiP2cYeL+Y6dgP9SC0+5CGqWFhQ5H+8wezPgAkAqFTw==","shasum":"b0c6be1a3663cf5d35566a2090953d2468b597eb","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.1.1-rc.tgz","fileCount":5,"unpackedSize":1252977,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCICS/3eNUjfnjl9ue2HI3EaAvBkbTg3DIk/twuLxAr3O+AiEA7adRCdyg+Ls4X5GHT2DuyhxXqYcuyw76ErvgcT9mvtk="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.1.1-rc_1703114442666_0.07943566683129522"},"_hasShrinkwrap":false},"5.1.3":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.1.3","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.1.3","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-xzB3cTJ+DCxnI/OeuZ/pkj9F9jQp/smgyajuaQlL6krfzd6sAcb9zVrCAxmqjJ9Am65PiSRpG0ok+Al86mybmA==","shasum":"1070d0a7843dc7e5087a09172bb4ba94c28a0708","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.1.3.tgz","fileCount":5,"unpackedSize":1253259,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC72BfU/eW4xfvOyLQZBtKKwEPsSuTx2wCqVWkKbvqgCAIhAOaTgKTd9/knMCnMVOSupRWTvYL1AbY2sfSr6hIRagND"}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.1.3_1703114493516_0.8542475815674389"},"_hasShrinkwrap":false},"5.1.5":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.1.5","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.1.5","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-UlRQlg9lgn10Rs/nkbnSYGLUgT/5xRxzaeRnjcYcfov+jby0mHutVke+Yw97JQ1M6ZN9DmuAApXgTabpZLL1KQ==","shasum":"c346fa10a78a20f4387c07110b793a42f5f43b67","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.1.5.tgz","fileCount":5,"unpackedSize":1253222,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICUk1OulnpV+1KZhMDaPaKbvCt550lbwDVh2hNC/sbP0AiAhtpKY+a4G6EfELTNKCPEer58TLj71GcTc4HvdVgGBXw=="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.1.5_1703114541350_0.5015100772855019"},"_hasShrinkwrap":false},"5.1.6":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.1.6","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.1.6","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-7OxKajJcA2CUVxytMvJfAHGRT184pOF6Ny1mU+dd9dStqOeH7v7fT7k9d7jsFdcQz/aM+OIZhieSY4ofidfhJg==","shasum":"891894cda5dc5ff6195cf527fc6989ea090d0177","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.1.6.tgz","fileCount":5,"unpackedSize":1253222,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIG9e+qYF64gdIxiZ1LTltz9vBd+xriipSuJMeTCbe2m+AiAnyZlcBGo0rQ9N0UpuHD0aECfcrOcDGu3rbTehFoC+hQ=="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.1.6_1703114586806_0.08591706884233896"},"_hasShrinkwrap":false},"5.2.0-beta":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.2.0-beta","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.2.0-beta","readme":"# ⚠️ Do not use this unless you understand the risks ⚠️\n\nYou’re probably better off using [ts-expose-internals](https://github.com/nonara/ts-expose-internals) directly.\n\n# ts-expose-internals-conditionally\n\nA simple fork of the excellent [ts-expose-internals](https://github.com/nonara/ts-expose-internals), but only activates when compiled with:\n\n```json5\n// tsconfig.json\n{\n  \"compilerOptions\": {\n    \"module\": \"nodenext\", // or \"node16\" or \"bundler\" - must support package.json \"exports\"\n    \"customConditions\": [\"ts-expose-internals\"]\n  }\n}\n```\n\n## Why?\n\nIf you are publishing a library that uses ts-expose-internals in its implementation, and exposes some of TypeScript’s _non-internal_ types in its API, your own declaration files will end up referencing ts-expose-internals:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals\" />\n\nimport { CompilerOptions } from \"typescript\";\nexport function doSomethingWrappingTypeScript(\n  fileName: string,\n  typeScriptOptions: CompilerOptions\n): unknown;\n```\n\nEven though `CompilerOptions` is part of TypeScript’s public API, ts-expose-internals is a module augmentation that re-declares and augments everything in the `typescript` module. So when `tsc --declaration` notices that the `CompilerOptions` you’re referencing in your own compilation is declared in `\"typescript\"` but augmented in `\"ts-expose-internals\"`, it adds an explicit reference to `\"ts-expose-internals\"` to make sure everyone using your library sees the same `CompilerOptions` that you do.\n\nNormally, this is a very desirable behavior. Without it, users could end up with types in their `node_modules` that reference things that don’t exist in their own compilation, leading to errors. But in the case of ts-expose-internals, you probably _don’t_ want to expose all of TypeScript’s internals for all of your users. You want the internals when compiling your own implementation code, but your public API can be consumed without them.\n\nBy using `ts-expose-internals-conditionally` and compiling with `\"customConditions\": [\"ts-expose-internals\"]` in your tsconfig.json, your compilation will include the ts-expose-internals module augmentation, but your users’ compilations won’t (assuming they don’t also have `\"customConditions\": [\"ts-expose-internals\"]`).\n\nOf course, this is **not safe**, because if you accidentally reference anything internal that makes it into your declaration files, your users will get errors:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals-conditionally\" />\n//  ^ references an empty file for users!\n\nimport { ModeAwareCache } from \"typescript\";\n//       ^^^^^^^^^^^^^^\n// Module \"typescript\" has no exported member 'ModeAwareCache'.\n```\n\nTo be safe, you should re-check your output declaration files _without_ any `customConditions` to ensure they’re portable.\n\n## This must go in `dependencies`, not `devDependencies`\n\nSince `tsc --declaration` will emit a reference to `\"ts-expose-internals-conditionally\"` in your declaration files, you need to ensure that reference actually resolves (to an empty file) for your users, which means they will need this package installed, which means it should go in your `dependencies`, not your `devDependencies`.\n\n## Why is this a fork and not an intermediate dependency?\n\nI thought I would get away with making a package with two tiny files:\n\n```ts\n// index.d.ts\n/// <reference types=\"ts-expose-internals\" />\n```\n\n```ts\n// empty.d.ts\n```\n\nBut it turns out that `tsc --declaration` still emits a reference directly to `\"ts-expose-internals\"`, even when it’s referenced transitively through this proxy package. This behavior actually makes sense, so I don’t think there was a way to do this without publishing an independent package.\n","readmeFilename":"README.md","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-WfO/WvY+pv9KLtBUV1sEQXst3+Cs9/sNDju8YOm+9LikASYME4OmfI62sof7IuyO06ZVHlbI3GsbGX3166E59w==","shasum":"1067aa0fd431f5df1c5e04183334d40e38108886","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.2.0-beta.tgz","fileCount":5,"unpackedSize":1265735,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBZhinTuY5RWuTAvoblfqUxUPUQwuVh0HLmoSVIZ2JI3AiEAmZ17S+6AiILudBHGkwpY7IqMibjVnUDxBeCON4FPyu0="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.2.0-beta_1703114636696_0.734838592313986"},"_hasShrinkwrap":false},"5.2.1-rc":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.2.1-rc","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.2.1-rc","readme":"# ⚠️ Do not use this unless you understand the risks ⚠️\n\nYou’re probably better off using [ts-expose-internals](https://github.com/nonara/ts-expose-internals) directly.\n\n# ts-expose-internals-conditionally\n\nA simple fork of the excellent [ts-expose-internals](https://github.com/nonara/ts-expose-internals), but only activates when compiled with:\n\n```json5\n// tsconfig.json\n{\n  \"compilerOptions\": {\n    \"module\": \"nodenext\", // or \"node16\" or \"bundler\" - must support package.json \"exports\"\n    \"customConditions\": [\"ts-expose-internals\"]\n  }\n}\n```\n\n## Why?\n\nIf you are publishing a library that uses ts-expose-internals in its implementation, and exposes some of TypeScript’s _non-internal_ types in its API, your own declaration files will end up referencing ts-expose-internals:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals\" />\n\nimport { CompilerOptions } from \"typescript\";\nexport function doSomethingWrappingTypeScript(\n  fileName: string,\n  typeScriptOptions: CompilerOptions\n): unknown;\n```\n\nEven though `CompilerOptions` is part of TypeScript’s public API, ts-expose-internals is a module augmentation that re-declares and augments everything in the `typescript` module. So when `tsc --declaration` notices that the `CompilerOptions` you’re referencing in your own compilation is declared in `\"typescript\"` but augmented in `\"ts-expose-internals\"`, it adds an explicit reference to `\"ts-expose-internals\"` to make sure everyone using your library sees the same `CompilerOptions` that you do.\n\nNormally, this is a very desirable behavior. Without it, users could end up with types in their `node_modules` that reference things that don’t exist in their own compilation, leading to errors. But in the case of ts-expose-internals, you probably _don’t_ want to expose all of TypeScript’s internals for all of your users. You want the internals when compiling your own implementation code, but your public API can be consumed without them.\n\nBy using `ts-expose-internals-conditionally` and compiling with `\"customConditions\": [\"ts-expose-internals\"]` in your tsconfig.json, your compilation will include the ts-expose-internals module augmentation, but your users’ compilations won’t (assuming they don’t also have `\"customConditions\": [\"ts-expose-internals\"]`).\n\nOf course, this is **not safe**, because if you accidentally reference anything internal that makes it into your declaration files, your users will get errors:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals-conditionally\" />\n//  ^ references an empty file for users!\n\nimport { ModeAwareCache } from \"typescript\";\n//       ^^^^^^^^^^^^^^\n// Module \"typescript\" has no exported member 'ModeAwareCache'.\n```\n\nTo be safe, you should re-check your output declaration files _without_ any `customConditions` to ensure they’re portable.\n\n## This must go in `dependencies`, not `devDependencies`\n\nSince `tsc --declaration` will emit a reference to `\"ts-expose-internals-conditionally\"` in your declaration files, you need to ensure that reference actually resolves (to an empty file) for your users, which means they will need this package installed, which means it should go in your `dependencies`, not your `devDependencies`.\n\n## Why is this a fork and not an intermediate dependency?\n\nI thought I would get away with making a package with two tiny files:\n\n```ts\n// index.d.ts\n/// <reference types=\"ts-expose-internals\" />\n```\n\n```ts\n// empty.d.ts\n```\n\nBut it turns out that `tsc --declaration` still emits a reference directly to `\"ts-expose-internals\"`, even when it’s referenced transitively through this proxy package. This behavior actually makes sense, so I don’t think there was a way to do this without publishing an independent package.\n","readmeFilename":"README.md","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-JuRR2q0ASLy4yQBM0dh6Pr/PPQ4rC13XF8cwsQ+q9kmhqqhJxMksv/GvoJlTEEyJhUUscARgMYDxR5TbyU9LAg==","shasum":"143ec691068bad87a4e454e019bc800264aa6168","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.2.1-rc.tgz","fileCount":5,"unpackedSize":1267164,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDrMdlJnpcVotr7Zv1K2Y0ue43zbjSfX++BOQSuGYa5UwIhAJ4hrTPB805GTzfTJkRcycDkDgXTAw9yp5IAzSRH3bw7"}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.2.1-rc_1703114686345_0.5293548329128495"},"_hasShrinkwrap":false},"5.2.2":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.2.2","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.2.2","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-WtJjkvyWMa4WnaWE60rc7dXRjnyHNRHFhhgbDRZfAqfvEV01+L/wu0h9bzBsCDAVDt3ScGTnoDtk+Wo4NdZqRQ==","shasum":"1e9e5cbbccd16cf6820eaa6e4579f5e6b7471406","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.2.2.tgz","fileCount":5,"unpackedSize":1267161,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCjNXc8/HMUFGQsUB1wj3x3W4tfZKWyRtKsv0CV5rhETwIhAOw5MuYUWVOKl/ekRcHW7SrM6JLbnZcMlF+FStUXLlWu"}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.2.2_1703114736843_0.9705007913083907"},"_hasShrinkwrap":false},"5.3.1-rc":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.3.1-rc","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.3.1-rc","readme":"# ⚠️ Do not use this unless you understand the risks ⚠️\n\nYou’re probably better off using [ts-expose-internals](https://github.com/nonara/ts-expose-internals) directly.\n\n# ts-expose-internals-conditionally\n\nA simple fork of the excellent [ts-expose-internals](https://github.com/nonara/ts-expose-internals), but only activates when compiled with:\n\n```json5\n// tsconfig.json\n{\n  \"compilerOptions\": {\n    \"module\": \"nodenext\", // or \"node16\" or \"bundler\" - must support package.json \"exports\"\n    \"customConditions\": [\"ts-expose-internals\"]\n  }\n}\n```\n\n## Why?\n\nIf you are publishing a library that uses ts-expose-internals in its implementation, and exposes some of TypeScript’s _non-internal_ types in its API, your own declaration files will end up referencing ts-expose-internals:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals\" />\n\nimport { CompilerOptions } from \"typescript\";\nexport function doSomethingWrappingTypeScript(\n  fileName: string,\n  typeScriptOptions: CompilerOptions\n): unknown;\n```\n\nEven though `CompilerOptions` is part of TypeScript’s public API, ts-expose-internals is a module augmentation that re-declares and augments everything in the `typescript` module. So when `tsc --declaration` notices that the `CompilerOptions` you’re referencing in your own compilation is declared in `\"typescript\"` but augmented in `\"ts-expose-internals\"`, it adds an explicit reference to `\"ts-expose-internals\"` to make sure everyone using your library sees the same `CompilerOptions` that you do.\n\nNormally, this is a very desirable behavior. Without it, users could end up with types in their `node_modules` that reference things that don’t exist in their own compilation, leading to errors. But in the case of ts-expose-internals, you probably _don’t_ want to expose all of TypeScript’s internals for all of your users. You want the internals when compiling your own implementation code, but your public API can be consumed without them.\n\nBy using `ts-expose-internals-conditionally` and compiling with `\"customConditions\": [\"ts-expose-internals\"]` in your tsconfig.json, your compilation will include the ts-expose-internals module augmentation, but your users’ compilations won’t (assuming they don’t also have `\"customConditions\": [\"ts-expose-internals\"]`).\n\nOf course, this is **not safe**, because if you accidentally reference anything internal that makes it into your declaration files, your users will get errors:\n\n```ts\n// your-library/index.d.ts\n\n/// <reference types=\"ts-expose-internals-conditionally\" />\n//  ^ references an empty file for users!\n\nimport { ModeAwareCache } from \"typescript\";\n//       ^^^^^^^^^^^^^^\n// Module \"typescript\" has no exported member 'ModeAwareCache'.\n```\n\nTo be safe, you should re-check your output declaration files _without_ any `customConditions` to ensure they’re portable.\n\n## This must go in `dependencies`, not `devDependencies`\n\nSince `tsc --declaration` will emit a reference to `\"ts-expose-internals-conditionally\"` in your declaration files, you need to ensure that reference actually resolves (to an empty file) for your users, which means they will need this package installed, which means it should go in your `dependencies`, not your `devDependencies`.\n\n## Why is this a fork and not an intermediate dependency?\n\nI thought I would get away with making a package with two tiny files:\n\n```ts\n// index.d.ts\n/// <reference types=\"ts-expose-internals\" />\n```\n\n```ts\n// empty.d.ts\n```\n\nBut it turns out that `tsc --declaration` still emits a reference directly to `\"ts-expose-internals\"`, even when it’s referenced transitively through this proxy package. This behavior actually makes sense, so I don’t think there was a way to do this without publishing an independent package.\n","readmeFilename":"README.md","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-ukdT2FS/lbbOMT27jsPuAPux/KnJ43QqAHzW2lG9WuLeu6obq8LzlfJ5QvMR2v5ffMxnBCiGBNlI7jOrbC6GyQ==","shasum":"3a0ee73eee972804b5949dc31ba9f2df7dfd435c","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.3.1-rc.tgz","fileCount":5,"unpackedSize":1511425,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEQA123UORl218nUZzm3FINAaX7xSwKJ5AdDQvWVigHnAiEAz6FagH8Bn/aLawV9vKmej0YkDjdz1roOi6HgWfRk3rA="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.3.1-rc_1703114835386_0.9251022869806858"},"_hasShrinkwrap":false},"5.3.2":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.3.2","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.3.2","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-WJGSCCHI0KzJTgIc6JyycUav3dsQdNKAzQGYIVJpM42GyZa3O2v2kL1gW+i6kFk2kWWrrSq20A9mE/Vk74zlRQ==","shasum":"a3b49fb97891422bbf1451d8c7c75dc72449b6cd","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.3.2.tgz","fileCount":5,"unpackedSize":1511436,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICtZQZypjv2r721+s1yOBc3HOIga4T3VWg3x6tOgIv+WAiBPvWvzLeHjVxsj31fyYVbPkEub8V5wTaT+CDiB1Q6NBg=="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.3.2_1703114888797_0.2155307966175315"},"_hasShrinkwrap":false},"5.3.3":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"5.3.3","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"exports":{"ts-expose-internals":"./index.d.ts","default":"./empty.d.ts"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@5.3.3","types":"./index.d.ts","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-k3wz3FnxrtuD8ue3Y9GmqEsph3PB1YCZs6zWy6d6T60A9/0zgy3w0wQBQOdKPoyWN0T+JQCbY5cE8Cg80VlzNw==","shasum":"c928024346702aab4d944138a636fc09598feb8e","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-5.3.3.tgz","fileCount":5,"unpackedSize":1511507,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCRHE3tCosCxuancKGQ3d99BcZ90t+OBBSl9YKe27n3mgIgV+Uk+rX0RiUuSEH2ek6fI7bHo7xdN+FaeqLg3NiJu6o="}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_5.3.3_1703114941516_0.7366254048840368"},"_hasShrinkwrap":false},"1.0.0-empty.0":{"name":"ts-expose-internals-conditionally","description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","version":"1.0.0-empty.0","license":"MIT","author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"types":"./empty.d.ts","contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"keywords":["typescript","internal types","internals","byots","types"],"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"ts-expose-internals-conditionally@1.0.0-empty.0","gitHead":"8fabcb1e13e0c75f23ea0c2b834cdade3f3466b5","bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","_nodeVersion":"21.1.0","_npmVersion":"10.2.0","dist":{"integrity":"sha512-F8m9NOF6ZhdOClDVdlM8gj3fDCav4ZIFSs/EI3ksQbAAXVSCN/Jh5OCJDDZWBuBy9psFc6jULGDlPwjMYMhJDw==","shasum":"fd9e5acb481466b0f5936f6e246eb37d0c3ceb28","tarball":"https://registry.npmjs.org/ts-expose-internals-conditionally/-/ts-expose-internals-conditionally-1.0.0-empty.0.tgz","fileCount":2,"unpackedSize":909,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDdYDg/on2WSdT/GfRutWiabZz1D3KbktWfB7NVMiq/HQIhAJNAa3ahv+Rce+0IMncB7+6tSq+moC3tn+YgWg915l9S"}]},"_npmUser":{"name":"andrewbranch","email":"andrew@wheream.io"},"directories":{},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ts-expose-internals-conditionally_1.0.0-empty.0_1703115505552_0.6917799981833701"},"_hasShrinkwrap":false}},"time":{"created":"2023-12-20T23:17:24.986Z","5.0.2":"2023-12-20T23:17:25.337Z","modified":"2023-12-20T23:38:25.874Z","5.0.3":"2023-12-20T23:18:13.397Z","5.0.4":"2023-12-20T23:19:03.379Z","5.1.0-beta":"2023-12-20T23:19:51.970Z","5.1.1-rc":"2023-12-20T23:20:42.963Z","5.1.3":"2023-12-20T23:21:33.771Z","5.1.5":"2023-12-20T23:22:21.636Z","5.1.6":"2023-12-20T23:23:07.058Z","5.2.0-beta":"2023-12-20T23:23:56.977Z","5.2.1-rc":"2023-12-20T23:24:46.599Z","5.2.2":"2023-12-20T23:25:37.115Z","5.3.1-rc":"2023-12-20T23:27:15.683Z","5.3.2":"2023-12-20T23:28:09.122Z","5.3.3":"2023-12-20T23:29:01.825Z","1.0.0-empty.0":"2023-12-20T23:38:25.698Z"},"maintainers":[{"name":"andrewbranch","email":"andrew@wheream.io"}],"description":"Augment the TypeScript compiler module's types to expose hidden internal types when tsconfig.json contains \"ts-expose-internals\" in `customConditions`.","homepage":"https://github.com/andrewbranch/ts-expose-internals-conditionally#readme","keywords":["typescript","internal types","internals","byots","types"],"repository":{"type":"git","url":"git+ssh://git@github.com/andrewbranch/ts-expose-internals-conditionally.git"},"contributors":[{"name":"Ron Spickenagel","url":"https://twitter.com/ron"},{"name":"Andrew Branch","email":"andrew@wheream.io"}],"author":{"name":"Andrew Branch","email":"andrew@wheream.io"},"bugs":{"url":"https://github.com/andrewbranch/ts-expose-internals-conditionally/issues"},"license":"MIT","readme":"ERROR: No README data found!","readmeFilename":""}