Weave Code
Openapi Runtime Laravel Package
jane/openapi-runtime
Deprecated runtime package for Jane OpenAPI. This repository is no longer maintained; development has moved to the main janephp/janephp project. Use that repo for current OpenAPI runtime components and updates.
DEPRECATED See https://github.com/janephp/janephp
Frequently asked questions about Openapi Runtime
- Why is jane/openapi-runtime deprecated, and should I still use it in Laravel?
- This package is deprecated since 2016 and lacks Laravel compatibility. It’s tied to JanePHP, a now-defunct OpenAPI codegen tool, and doesn’t support modern OpenAPI 3.x specs or Laravel’s service container. Use alternatives like php-openapi/client or darkaonline/l5-swagger instead.
- How do I migrate from JanePHP-generated clients to a Laravel-compatible OpenAPI client?
- Audit your JanePHP-generated code for Laravel-specific gaps (e.g., middleware, route binding). Test compatibility with Laravel’s HTTP layer (Guzzle/Symfony HTTP Client). If integration fails, replace with php-openapi/client, which supports OpenAPI 3.x and PSR-18 HTTP clients.
- Does jane/openapi-runtime work with Laravel’s dependency injection (Container) or Facades?
- No, this package lacks Laravel service providers or Facades. It assumes JanePHP’s codegen output, which isn’t compatible with Laravel’s Container or Facade system. You’d need to manually wrap it in a Laravel service provider, increasing technical debt.
- What are the PHP version compatibility risks with jane/openapi-runtime in Laravel?
- This package was written for PHP 5.6–7.x and may fail on PHP 8.x due to removed features like `create_function()` and changes in exception handling. Laravel typically requires PHP 8.0+, so conflicts are likely without extensive refactoring.
- Are there Laravel-specific alternatives to jane/openapi-runtime for OpenAPI clients?
- Yes, consider php-openapi/client (supports OpenAPI 3.x and PSR-18) or darkaonline/l5-swagger for Laravel. These integrate natively with Laravel’s HTTP clients, service providers, and modern PHP features.
- Can I use jane/openapi-runtime with Laravel’s Guzzle HTTP client or Symfony HTTP Client?
- No, this package doesn’t integrate with Laravel’s HTTP layer. It expects JanePHP-specific bootstrapping, which conflicts with Laravel’s Guzzle/Symfony HTTP Client integrations. Modern alternatives like php-openapi/client support these out of the box.
- What OpenAPI spec version does jane/openapi-runtime support, and is it compatible with Laravel?
- This package only supports OpenAPI 2.0 (Swagger), not the modern OpenAPI 3.x. Laravel applications typically use OpenAPI 3.x, so this package is a poor fit. Alternatives like php-openapi/client fully support OpenAPI 3.x.
- How do I test jane/openapi-runtime in a Laravel application before migration?
- Create a minimal Laravel service provider to wrap the JanePHP client and test initialization. Verify if it can bypass JanePHP-specific bootstrapping. If tests fail, document gaps and plan a migration to php-openapi/client or another modern tool.
- Are there security risks using jane/openapi-runtime in production with Laravel?
- Yes, this package hasn’t been updated since 2016 and lacks security patches for PHP/Laravel vulnerabilities. It also assumes JanePHP’s deprecated codegen, which may introduce undocumented risks. Migrate to a maintained alternative like php-openapi/client.
- What’s the best approach if my team is locked into JanePHP-generated clients?
- Assess whether the JanePHP-generated code can be refactored into a Laravel-compatible wrapper (high effort, low ROI). If not, prioritize migrating to php-openapi/client or another modern OpenAPI client. Document the migration path and test thoroughly before deployment.
Weaver
How can I help you explore Laravel packages today?