Weave Code
Dsn Laravel Package
zenstruck/dsn
A small PHP library for parsing and composing DSN (data source name) strings into structured objects, with support for custom schemes, validation, and clean access to connection credentials and options. Useful for configuring database and service connections from environment variables.
DSN parsing library with support for complex expressions.
Frequently asked questions about Dsn
- How do I install zenstruck/dsn in a Laravel app?
- Install it with Composer using composer require zenstruck/dsn:^1.0. There is no Laravel auto-discovery, service provider, config publish step, or Artisan command. You can adopt it in one pull request and revert it the same way because it is a leaf utility.
- Is zenstruck/dsn a Laravel package with a service provider?
- No. zenstruck/dsn is a framework-agnostic PHP library, not a Laravel package. It has no service provider, facade, config file, publishable assets, migrations, container bindings, or boot-cycle cost. In Laravel it belongs in the same layer as parse_url(), consumed by your own thin adapter when needed.
- Which Laravel versions does zenstruck/dsn support?
- There is no direct Laravel coupling, so Laravel 10, 11, and 12 compatibility reduces to whether your PHP version satisfies the package's PHP floor. Confirm that floor before planning work, especially because the v1.0.0 Symfony 8 support commit could affect require-dev only or could raise runtime constraints. Run composer why zenstruck/dsn and composer update --dry-run before committing.
- What can I use zenstruck/dsn for in a Laravel application?
- Use it to replace hand-rolled explode('://') or parse_url() handling for connection strings such as queues, mailers, cache, and search backends. It is also useful for normalizing DSNs from environment variables and for splitting DSNs for multi-host transports. The main win is safer, consistent access to credentials and options instead of ad-hoc string handling.
- How do I parse a DSN string and access credentials with zenstruck/dsn?
- Pass a DSN such as mysql://user:pass@localhost:3306/app?charset=utf8 into the parser and receive an immutable value object. The object exposes getters for scheme, credentials, host, port, path, query parameters, and fragment. Query parameters are available as structured data rather than raw strings.
- Can zenstruck/dsn build DSN strings from individual components?
- Yes. The library supports composing DSNs from individual components as well as parsing existing DSN strings. That makes it useful when your Laravel configuration code needs to construct connection URLs from environment values or service settings. The resulting DSN can then be passed to the transport or client that expects a connection string.
- Does zenstruck/dsn validate DSNs and support custom schemes?
- Yes. It parses DSNs into a validated, consistent object and supports custom schemes. Invalid or inconsistent input is handled through parsing rather than leaving you with loosely structured arrays. This is helpful when different services use different DSN schemes but you want one predictable access pattern.
- Is zenstruck/dsn safe to use in production and is it maintained?
- It is a low-risk leaf utility with no boot cycle, global state, or container coupling, which makes production integration straightforward. Two caveats are worth recording: the 0.2.0 to 1.0.0 jump crosses a pre-1.0 semver boundary, and the release notes are a commit list rather than a curated changelog. Also note the single-maintainer bus factor and review the changelog or diff before upgrading.
- What are alternatives to zenstruck/dsn for parsing DSNs in PHP?
- PHP's built-in parse_url() is the common alternative and is already available in Laravel applications. zenstruck/dsn adds a structured immutable value object, validation, custom scheme support, and clean access to credentials and query parameters. If you only need one simple URL split, parse_url() may be enough; if DSN handling is spread across your codebase, this package can remove duplication and bugs.
- Does zenstruck/dsn work with PHP 8.4 and Symfony 8, and are there breaking changes from 0.2 to 1.0?
- v1.0.0 includes Symfony 8 support and deprecation fixes aimed at PHP 8.4 readiness, but you should verify whether Symfony 8 is confined to require-dev or affects runtime constraints. The 0.2.0 to 1.0.0 upgrade spans a pre-1.0 boundary, so treat it as a minor migration rather than a patch bump. Review the changelog or diff for signature, exception, constructor visibility, or immutability changes, then confirm with composer why and composer update --dry-run.
Weaver
How can I help you explore Laravel packages today?