Pandoc Laravel Package

Product Decisions This Supports

• Feature and integration: The new noStandalone() method gives programmatic control to disable --standalone, reducing the need for workarounds, custom forks, or test-only hacks when embedding the package in Laravel commands, CI pipelines, or internal tooling.
• Roadmap signal: This is an incremental configurability improvement in a pre-1.0 package. It suggests the maintainers are maturing the API surface, but it does not imply API stability.
• Build vs buy: If your team needs fine-grained control over CLI behavior without maintaining a fork, this lowers the integration cost. If you only use default behavior, the feature does not change the buy case.
• Use cases: Custom Artisan commands, automated tests, package wrappers, environment-specific workflows, and any context where standalone mode should be off by default.

When to Consider This Package

• Consider adoption when you already use or are evaluating this Laravel/PHP package and need to disable --standalone programmatically, especially in tests, custom commands, or embedded workflows.
• Consider it when active maintenance and incremental configuration improvements matter more than a stable 1.0 API.
• Look elsewhere if you require backward-compatibility guarantees, if you have no use for standalone mode, or if your integration cannot tolerate pre-1.0 API changes. Validate the upgrade path and lock-in risk before broad adoption.

How to Pitch It (Stakeholders)

• Executives: This is a small, non-breaking feature release (0.9.0) that improves integration flexibility and signals active maintenance. It lowers custom work needed to fit the package into our workflows. Risk is low, but pre-1.0 status means we should pilot before broad rollout.
• Engineering: The new noStandalone() method lets you disable --standalone in code, which is useful for tests, custom Artisan commands, and embedded usage. No breaking changes are indicated in the release note. Adopt if you need programmatic control; otherwise defer until 1.0 if API stability is critical. Update internal docs and examples where relevant.