Auto-generate TypeScript clients for Django Ninja during runserver
Project description
Django Ninja TS Generator
Automatically builds your TypeScript client whenever your Django Ninja schema changes.
Installation
-
Install the package:
pip install django-ninja-ts
-
Add to
INSTALLED_APPSinsettings.py:INSTALLED_APPS = [ # ... 'django.contrib.staticfiles', 'django_ninja_ts', # Add this # ... ]
Migrating from v1.x
v2.0 switched from openapi-generator-cli (Node.js/Java) to openapi-ts-client (pure Python).
Breaking changes:
- Remove
NINJA_TS_CMD_ARGSfrom your settings (no longer supported) - Add
NINJA_TS_FORMATif you need axios or angular (fetch is default) - Node.js and Java are no longer required
Configuration
Add these settings to your settings.py:
import os
# Path to your NinjaAPI instance (dot notation)
NINJA_TS_API = 'myproject.api.api'
# Where to output the generated client
NINJA_TS_OUTPUT_DIR = os.path.join(BASE_DIR, '../frontend/src/app/shared/api')
# Optional: Client format - 'fetch' (default), 'axios', or 'angular'
NINJA_TS_FORMAT = 'fetch'
# Optional: Debounce time in seconds (prevents rapid rebuilds on "Save All")
# Default: 1.0
# NINJA_TS_DEBOUNCE_SECONDS = 0.5
# Optional: Clear output directory before generation
# Default: True
# NINJA_TS_CLEAN = True
# Optional: Enable/disable auto-generation on runserver
# Default: True
# NINJA_TS_AUTO_GENERATE = True
How It Works
- When you run
python manage.py runserver, the package intercepts the command - It loads your Django Ninja API and extracts the OpenAPI schema
- It calculates a hash of the schema and compares it to the previous build
- If the schema has changed, it runs
openapi-ts-clientto generate the TypeScript client - The hash is stored in
.schema.hashin the output directory to avoid unnecessary rebuilds
Configuration Options
| Setting | Required | Default | Description |
|---|---|---|---|
NINJA_TS_API |
Yes | - | Dot-notation path to your NinjaAPI instance |
NINJA_TS_OUTPUT_DIR |
Yes | - | Directory where the TypeScript client will be generated |
NINJA_TS_FORMAT |
No | fetch |
Client format: fetch, axios, or angular |
NINJA_TS_DEBOUNCE_SECONDS |
No | 1.0 |
Delay before generation to handle rapid file saves |
NINJA_TS_CLEAN |
No | True |
Clear output directory before generation |
NINJA_TS_AUTO_GENERATE |
No | True |
Enable auto-generation on runserver |
Example: Using Axios
NINJA_TS_FORMAT = 'axios'
Example: Using Angular
NINJA_TS_FORMAT = 'angular'
Example: Disabling Auto-Generation
If you prefer to generate the client manually instead of on every server restart:
NINJA_TS_AUTO_GENERATE = False
Manual Generation
You can manually generate the TypeScript client using the generate_ts_client command:
# Generate client (only if schema changed)
python manage.py generate_ts_client
# Force regeneration even if schema hasn't changed
python manage.py generate_ts_client --force
This is useful when:
- You've disabled auto-generation with
NINJA_TS_AUTO_GENERATE = False - You want to generate the client in CI/CD pipelines
- You need to regenerate without restarting the server
Logging
The package uses Python's standard logging module. To see debug output, configure logging in your settings:
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'handlers': {
'console': {
'class': 'logging.StreamHandler',
},
},
'loggers': {
'django_ninja_ts': {
'handlers': ['console'],
'level': 'DEBUG',
},
},
}
Troubleshooting
Common Issues
"Module not found" error
Problem: You see an error like Generation Error: Module not found: No module named 'myapp'
Solution: Ensure NINJA_TS_API contains a valid import path to your NinjaAPI instance:
# Correct - full import path
NINJA_TS_API = 'myapp.api.api'
# Incorrect - missing module path
NINJA_TS_API = 'api'
"does not have 'get_openapi_schema' method" error
Problem: The object at your NINJA_TS_API path is not a NinjaAPI instance.
Solution: Ensure you're pointing to the actual NinjaAPI instance, not a module or router:
# In myapp/api.py
from ninja import NinjaAPI
api = NinjaAPI() # This is what NINJA_TS_API should point to
# In settings.py
NINJA_TS_API = 'myapp.api.api' # Points to the 'api' variable in myapp/api.py
"Invalid OpenAPI schema" error
Problem: The schema returned by your API is missing required OpenAPI fields.
Solution: This usually indicates a configuration issue with your NinjaAPI. Ensure your API has:
- A title (set in NinjaAPI constructor or via
titleparameter) - At least one endpoint registered
api = NinjaAPI(title="My API", version="1.0.0")
@api.get("/health")
def health(request):
return {"status": "ok"}
"Output directory parent is not writable" error
Problem: The package cannot create files in the specified output directory.
Solution: Ensure the parent directory of NINJA_TS_OUTPUT_DIR exists and has write permissions:
# Check permissions
ls -la /path/to/parent/directory
# Fix permissions if needed
chmod 755 /path/to/parent/directory
Schema not regenerating after changes
Problem: You've made API changes but the TypeScript client isn't updating.
Solution:
- Delete the
.schema.hashfile in your output directory - Restart the development server
- If using
NINJA_TS_DEBOUNCE_SECONDS, wait for the debounce period
Configuration Validation
The package validates your configuration at startup using Django's system checks. Run checks manually with:
python manage.py check
This will report any configuration errors like:
- Missing required settings
- Invalid setting types
- Unwritable output directories
Debug Mode
Enable debug logging to see detailed information about the generation process:
LOGGING = {
'version': 1,
'loggers': {
'django_ninja_ts': {
'handlers': ['console'],
'level': 'DEBUG',
},
},
}
Contributing
Commit Messages
This project uses Conventional Commits for commit messages.
Format: <type>(<scope>): <description>
Types:
feat- New featuresfix- Bug fixesdocs- Documentation changesstyle- Code style changes (formatting, whitespace)refactor- Code refactoring without feature changestest- Adding or updating testschore- Maintenance tasks, dependencies, configs
Examples:
feat(generator): add support for axios client
fix(runserver): handle missing Java dependency gracefully
docs(readme): add troubleshooting section
License
MIT License - see LICENSE for details.
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file django_ninja_ts-2.1.0.tar.gz.
File metadata
- Download URL: django_ninja_ts-2.1.0.tar.gz
- Upload date:
- Size: 17.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
2d03fea10304a1e35e13ab630717a8d1030f36fdbf6e4d1f22684b212be674a2
|
|
| MD5 |
93fadde8ae2fc6fa8dc1a00eff6f5b85
|
|
| BLAKE2b-256 |
9fd76c72b11f590703a0a0154bfa1fb21b7cafe4c76e3b396ea2bac075b13b8d
|
Provenance
The following attestation bundles were made for django_ninja_ts-2.1.0.tar.gz:
Publisher:
release.yml on fa-krug/django-ninja-ts
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
django_ninja_ts-2.1.0.tar.gz -
Subject digest:
2d03fea10304a1e35e13ab630717a8d1030f36fdbf6e4d1f22684b212be674a2 - Sigstore transparency entry: 851719542
- Sigstore integration time:
-
Permalink:
fa-krug/django-ninja-ts@162642d3ad22db3c64bafa7a76443319aec4d657 -
Branch / Tag:
refs/heads/main - Owner: https://github.com/fa-krug
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@162642d3ad22db3c64bafa7a76443319aec4d657 -
Trigger Event:
push
-
Statement type:
File details
Details for the file django_ninja_ts-2.1.0-py3-none-any.whl.
File metadata
- Download URL: django_ninja_ts-2.1.0-py3-none-any.whl
- Upload date:
- Size: 12.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
3ec0f9e1da77c347c5736477bed5c92ac5426a545c29f62acc63e2721f8a7740
|
|
| MD5 |
7d014eaff9c3bb3314cb7baace7a2600
|
|
| BLAKE2b-256 |
cd1a25ae4a528d0b592772209576298698c8576463fdfe161dbcf0d2982aafee
|
Provenance
The following attestation bundles were made for django_ninja_ts-2.1.0-py3-none-any.whl:
Publisher:
release.yml on fa-krug/django-ninja-ts
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
django_ninja_ts-2.1.0-py3-none-any.whl -
Subject digest:
3ec0f9e1da77c347c5736477bed5c92ac5426a545c29f62acc63e2721f8a7740 - Sigstore transparency entry: 851719556
- Sigstore integration time:
-
Permalink:
fa-krug/django-ninja-ts@162642d3ad22db3c64bafa7a76443319aec4d657 -
Branch / Tag:
refs/heads/main - Owner: https://github.com/fa-krug
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@162642d3ad22db3c64bafa7a76443319aec4d657 -
Trigger Event:
push
-
Statement type: