Generated types
Type feature names and pricing modes with the generated _orbyte.ts file.
The CLI generates _orbyte.ts after a successful deployment. It writes the file in src when that directory exists, otherwise beside the config. Commit this file with your application.
The file contains Credits and Features enums, plus a Plans enum when the config declares plans. Its values are stable catalog keys, so they work across Development and Production applications where you deployed the same catalog.
It also registers feature names and pricing modes with the SDK through TypeScript module augmentation. Include it in your tsconfig.json through include or files; a normal src/**/*.ts include covers it. TypeScript then rejects unknown names and string-based calls to callback features.
Regenerate the file after changing the catalog. The type declarations emit no runtime code and do not import orbyte.config.ts. Fixed-price features can use their names directly in check and track without a runtime config import. Callback prices require the feature object from your config. See the SDK reference and pricing.
Without generated types, string calls remain available for catalogs managed through the dashboard or HTTP API. Those names are checked by the API at runtime.