Registry / type-stubs / ts-expose-internals-conditionally

ts-expose-internals-conditionally

library1.0.0-empty.0jsnpmunverified

A type augmentation package that conditionally exposes TypeScript compiler internal types when the consuming project's tsconfig.json includes 'ts-expose-internals' in the `customConditions` field. Version 1.0.0-empty.0 is an empty placeholder, effectively doing nothing; there is no stable release with actual functionality. This is a proof-of-concept for conditional type augmentation, not for production use. The package ships with TypeScript type definitions and targets developers working on TypeScript compiler internals or tooling that requires access to hidden APIs.

type-stubs

npm install ts-expose-internals-conditionally

github ↗package ↗

INSTALL

IMPORT

SIG · TS-EXPOSE-INTERNAL

ts-expose-internals-conditionally

type-stubsjavascriptv1.0.0-empty.0

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

ts-expose-internals-conditionally

✓ import 'ts-expose-internals-conditionally'

✗ import * as ts from 'ts-expose-internals-conditionally'

This is a side-effect import; it augments the 'typescript' module globally when customConditions includes 'ts-expose-internals'.

Shows how to enable internal types by setting customConditions and importing the package as side-effect.

// tsconfig.json { "compilerOptions": { "customConditions": ["ts-expose-internals"] } } // any.ts (after importing the package) import 'ts-expose-internals-conditionally'; import ts from 'typescript'; // Now TypeScript's internal types (like `EnumType`) are accessible via `ts` const internalType: ts.EnumType = { /* ... */ };

Debug

Known issues

deprecatedPackage version 1.0.0-empty.0 is an empty placeholder with no functionality. Upgrade to a non-empty version or use alternative packages like 'ts-expose-internals'.

fix

Remove this dependency or wait for a future stable release.

affects: <=1.0.0-empty.0

gotchacustomConditions requires TypeScript 5.0+ and proper configuration in tsconfig.json. Without it, the import has no effect.

fix

Ensure tsconfig.json has 'customConditions' array containing 'ts-expose-internals'.

affects: >=0.0.0

breakingExposed internal types are unstable and may change between TypeScript versions, breaking your code.

fix

Pin your TypeScript version and test after updates.

affects: >=0.0.0

gotchaThis package only provides type augmentation; the actual TypeScript runtime does not export internals. Code using these types will not compile if you try to access them at runtime.

fix

Use only for type definitions; do not rely on runtime exports.

affects: >=0.0.0

deprecatedThe entire approach of conditionally exposing internals via customConditions is experimental and not officially supported by the TypeScript team.

fix

Consider using @ts-expose-internals or forking TypeScript.

affects: >=0.0.0

Errors

Common errors & fixes

Cannot find module 'ts-expose-internals-conditionally' or its corresponding type declarations.

Package not installed or version is empty placeholder with no actual module.

fix

Run npm install ts-expose-internals-conditionally@latest (once stable release exists) or use another package.

Module augmentation failed: 'typescript' does not have any internal types.

customConditions in tsconfig.json missing 'ts-expose-internals'.

fix

Add 'customConditions': ['ts-expose-internals'] to compilerOptions in tsconfig.json.

Upgrade

Version history

1.0.0-empty.0latest on npm

Audit

Dependencies

typescriptoptionalpeer dependency - the package augments the TypeScript compiler module's types

Agent activity

19 hits · last 30 days

node

OpenAI (training)

Amazon

Resources

githubhttps://github.com/andrewbranch/ts-expose-internals-conditionally ↗

packagehttps://www.npmjs.com/package/ts-expose-internals-conditionally ↗