Weave Code
Twig Js Bundle Laravel Package
forknetwork/twig-js-bundle
A Symfony bundle that integrates Twig.js so you can reuse Twig templates in the browser. It provides the wiring and helpers needed to load, compile, and render Twig templates client-side, bridging server-side Twig and front-end JavaScript.
Integrates twig.js into your Symfony2 application
Frequently asked questions about Twig Js Bundle
- Is forknetwork/twig-js-bundle a Laravel package?
- No. It is a Symfony2 bundle (ForkNetwork\TwigJsBundle) that wires Twig.js into Symfony's dependency injection container and asset pipeline. It has no Laravel service provider, no facades, and no awareness of Laravel's view layer or container. Adopting it in Laravel is a port project, not a normal Composer dependency.
- Can I use forknetwork/twig-js-bundle with Laravel Blade templates?
- No. The bundle only bridges Symfony's Twig environment to Twig.js, so Blade templates cannot be compiled or rendered by it. If your server-side templating is Blade, the isomorphic template-reuse benefit disappears entirely. You would be better served by a JSON/API contract plus a JavaScript component library.
- How do I install forknetwork/twig-js-bundle in a Laravel project?
- You cannot meaningfully install it as a Laravel package. Composer may download the code, but the bundle expects Symfony kernel, DI, and asset stack conventions and will not auto-register in Laravel. The realistic path is to skip the package and use twig.js directly from npm with a Vite or Webpack loader.
- What Laravel version does forknetwork/twig-js-bundle support?
- None. The package targets Symfony 2/3, and its last release was in March 2019. There is no official Laravel version support, no service provider, and no compatibility layer for Laravel's container or view system. Treat any Laravel usage as an unsupported fork.
- What is the best Laravel alternative for rendering Twig templates in the browser?
- Use twig.js directly from npm and add a Vite plugin or precompile step that turns .twig files into JavaScript template functions. Mirror the template directory under resources and ship the compiled output with your front-end bundle. This avoids abandoned PHP code and keeps the integration inside your existing build pipeline.
- Does forknetwork/twig-js-bundle work with PHP 8.2 and PHP 8.3?
- It has not been verified on modern PHP. The bundle relies on Symfony 2 APIs that were removed or renamed in later Symfony majors, so even Symfony shops face an upgrade exercise. Before considering it, test template compilation and autoescaping behavior on your target PHP version.
- Is forknetwork/twig-js-bundle maintained and safe for production?
- No, it is not a safe default for production. The last release was 2019-03-14, it has roughly 3 stars and 0 dependents, and there is no active maintainer for issue triage or security response. Template compilation and autoescaping are exactly where server/client divergence can become an XSS vector, and that surface is unreviewed.
- How does the Symfony asset pipeline integration work, and can I replicate it in Laravel with Vite?
- The bundle plugs Twig.js template loading and compilation into Symfony's DI container and asset stack so templates can be served to the browser. In Laravel you can replicate the useful part with a Vite plugin that transforms .twig files into JavaScript template functions. That approach adds no PHP dependency and keeps everything in your front-end build.
- Can I fork forknetwork/twig-js-bundle and add a Laravel service provider?
- Yes, but budget for perpetual ownership. Strip the Symfony Extension and CompilerPass layer, republish the compilation logic as a standalone Composer library, and add an optional Laravel service provider pinned internally. Only do this if the bundle contains non-trivial Twig-to-JS compilation logic worth preserving.
- What are the alternatives to forknetwork/twig-js-bundle for sharing templates between PHP and JavaScript?
- The preferred route is twig.js directly with a Vite or Webpack loader that precompiles shared templates. Other options include a JSON/API contract with a JavaScript component library, or a maintained isomorphic templating solution if Twig is a hard constraint. The abandoned Symfony bundle should not be in the critical path.
Weaver
How can I help you explore Laravel packages today?