Weave Code
Terms Module Snappy Bundle Laravel Package
rich-id/terms-module-snappy-bundle
A Laravel module from rich-id that bundles terms and conditions handling with Snappy PDF support, so you can manage, render, and serve policy documents from a single package. Note: minimal adoption and metadata; review the source before use. (219 characters)
At a glance
Frequently asked questions about Terms Module Snappy Bundle
- How do I install rich-id/terms-module-snappy in a Laravel application?
- Install it with Composer using composer require rich-id/terms-module-snappy, then check whether the package registers a Laravel service provider via auto-discovery or uses Symfony bundle conventions. Publish any configuration with php artisan vendor:publish and confirm the expected wkhtmltopdf binary path. Because v1.0.0 is the first tagged release with a minimal changelog, audit composer.json and the source layout before wiring it into an existing app.
- Does rich-id/terms-module-snappy support Laravel 10 and Laravel 11?
- The package metadata and v1.0.0 release notes do not document supported Laravel, PHP, or Symfony versions, so treat compatibility as unverified. Inspect composer.json constraints and test installation in an isolated branch or container against your target Laravel version. Do not assume Laravel 10 or 11 support until you have confirmed it yourself.
- Is this a Laravel package or a Symfony bundle?
- The repository name ends in -bundle, which is a compatibility red flag because Symfony bundles and Laravel packages use different registration, config, and view conventions. The description says it provides Laravel service and controller bindings, but the release notes do not confirm Laravel-native wiring. Inspect the source for a Laravel service provider and auto-discovery before assuming it drops into a Laravel app.
- Does rich-id/terms-module-snappy store terms and conditions or only render PDFs?
- The only changelog entry for v1.0.0 is an initial Snappy generator version note, which suggests the inaugural scope is a wrapper around Snappy HTML-to-PDF conversion rather than a full terms lifecycle module. The package description mentions a ready-to-use terms module, but it is unlikely to own persistence, versioning, publication, or acceptance evidence at this release. Plan to build and own the terms domain yourself and use this only as a renderer if you adopt it.
- Do I need wkhtmltopdf installed to use this Snappy bundle?
- Yes. Snappy is an HTML-to-PDF adapter that shells out to the wkhtmltopdf binary, so the executable must be installed and available to your PHP process. That external binary dependency is a poor fit for serverless platforms and hardened containers, and it introduces process-level failure modes and font rendering inconsistencies. Confirm your deployment environment can run wkhtmltopdf before committing to the package.
- How do I configure terms PDF templates and layouts with this package?
- The package advertises publishable configuration and configurable templates and layout options, so start by publishing the config and inspecting the available template and layout keys. The v1.0.0 release notes contain no setup detail, so expect to read the config file and source to understand the expected view paths and options. Render a sample terms document early to confirm the templates behave as you expect.
- Is rich-id/terms-module-snappy safe for compliance-sensitive legal documents?
- Treat it with caution. The package has zero stars, zero dependents, and no prior release history, and terms and conditions are compliance-sensitive content that should not flow through an unvetted dependency without a fork-and-own decision. Snappy and wkhtmltopdf add HTML injection, temp-file handling, and unmaintained rendering engine risks. If you adopt it, wrap it behind your own terms domain and keep acceptance evidence in code you control.
- Does rich-id/terms-module-snappy ship migrations, routes, views, and tests?
- That is unknown from the release metadata. v1.0.0 is tagged as an initial Snappy generator version and the notes say nothing about migrations, routes, views, or test coverage. Audit the repository tree and run the test suite in an isolated environment before deciding whether the package gives you anything beyond PDF rendering.
- What are good alternatives to rich-id/terms-module-snappy for Laravel PDF generation?
- For most teams a maintained PDF library plus an in-house terms model is a better fit than this package. Options include well-supported HTML-to-PDF tools such as dompdf, Browsershot, and maintained Snappy wrappers, paired with your own models for terms versions, publication, and acceptance records. Choosing a maintained library also gives you clearer security advisory tracking and upgrade discipline.
- What is the 1.x upgrade and maintenance policy for this package?
- No upgrade discipline is demonstrated. A 1.0.0 tag earned by a single initial-version commit implies no soak time and no patch history, so any 1.x minor release should be treated as potentially breaking. If you depend on it, fork it with a named owner and pin exact versions rather than relying on caret constraints.
Weaver
How can I help you explore Laravel packages today?