Skip to main content

Composer Install Force PHP

Install composer dependencies ignoring PHP version

When working with PHP projects, you often encounter situations where the required PHP version for a package is slightly different from the one you have installed locally. While it's generally recommended to stick to the specified version, there are cases where minor version differences might not be critical. In such scenarios, you can instruct Composer to ignore the platform requirements and proceed with the installation.

Composer install ignoring PHP version

Composer provides a handy flag "--ignore-platform-reqs" that allows you to bypass platform checks, including PHP version requirements. This can be particularly useful when you're confident that the minor version difference won't affect the package's functionality in your project.

For instance, let's say a package you want to install requires PHP 8.2, but you have PHP 8.3 installed. In this case, you can use the following command to install the package while ignoring the PHP version requirement:

composer install --ignore-platform-req=php

This command tells Composer to disregard the platform requirements specifically for PHP, allowing the installation to proceed even though your PHP version doesn't precisely match the requirement.

However, it's crucial to exercise caution when using this flag. Ignoring platform requirements can sometimes lead to unexpected issues if the package relies on features or behaviors specific to the required PHP version. Therefore, it's essential to thoroughly test your application after installing packages with ignored platform requirements to ensure everything functions as expected.

Popular posts from this blog

Undefined global vim

Defining vim as global outside of Neovim When developing plugins for Neovim, particularly in Lua, developers often encounter the "Undefined global vim" warning. This warning can be a nuisance and disrupt the development workflow. However, there is a straightforward solution to this problem by configuring the Lua Language Server Protocol (LSP) to recognize 'vim' as a global variable. Getting "Undefined global vim" warning when developing Neovim plugin While developing Neovim plugins using Lua, the Lua language server might not recognize the 'vim' namespace by default. This leads to warnings about 'vim' being an undefined global variable. These warnings are not just annoying but can also clutter the development environment with unnecessary alerts, potentially hiding other important warnings or errors. Defining vim as global in Lua LSP configuration to get rid of the warning To resolve the "Undefined global vi...
Read more

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo...
Read more

CopilotChat GlobFile Configuration

CopilotChat GlobFile Configuration Want to feed multiple files into GitHub Copilot Chat from Neovim without listing each one manually? Let's add a tiny feature that does exactly that: a file glob that includes full file contents . In this post, we'll walk through what CopilotChat.nvim offers out of the box, why the missing piece matters, and how to implement a custom #file_glob:<pattern> function to include the contents of all files matching a glob. Using Copilot Chat with Neovim CopilotChat.nvim brings GitHub Copilot's chat right into your editing flow. No context switching, no browser hopping — just type your prompt in a Neovim buffer and let the AI help you refactor code, write tests, or explain tricky functions. You can open the chat (for example) with a command like :CopilotChat , then provide extra context using built-in functions. That “extra context” is where the magic really happens. Built-in functio...
Read more