@symfony/ux-google-map
Advanced tools
GoogleMaps bridge for Symfony UX Map, integrate interactive maps in your Symfony applications
JavaScript assets of the symfony/ux-google-map PHP package.
This npm package is reserved for advanced users who want to decouple their JavaScript dependencies from their PHP dependencies (e.g., when building Docker images, running JavaScript-only pipelines, etc.).
We strongly recommend not installing this package directly, but instead install the PHP package symfony/ux-google-map in your Symfony application with Flex enabled.
If you still want to install this package directly, please make sure its version exactly matches symfony/ux-google-map PHP package version:
composer require symfony/ux-google-map:2.23.0
npm add @symfony/ux-google-map@2.23.0
Tip: Your package.json file will be automatically modified by Flex when installing or upgrading a PHP package. To prevent this behavior, ensure to use at least Flex 1.22.0 or 2.5.0, and run composer config --json "extra.symfony/flex.synchronize_package_json" false.
FAQs
GoogleMaps bridge for Symfony UX Map, integrate interactive maps in your Symfony applications
We found that @symfony/ux-google-map demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.
Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.
Security News
The planned feature introduces a review step before releases go live, following the Shai-Hulud attacks and a rocky migration off classic tokens that disrupted maintainer workflows.