Install latest composer dependencies
up vote
0
down vote
favorite
I have private repository in which we have a composer.json file.
{
"name": "vendor/package",
"version": "1.1.0",
"type": "project",
"require": {
"craftcms/cms": "^3.0.0",
"ether/splash": "^v3.0.2",
"ether/simplemap": "^v3.3.4",
"aelvan/imager": "^v2.1.1",
"vlucas/phpdotenv": "^2.4.0",
"craftcms/redactor": "^2.1.6",
"craftcms/mandrill": "^1.2.0",
"sebastianlenz/linkfield": "^1.0.15",
"solspace/craft3-freeform": "^2.4.1",
"nystudio107/craft-minify": "^1.2.9",
"nystudio107/craft-seomatic": "^3.1.26",
"pieterxjan/slack-error-notifications": "^1.0"
},
"autoload": {
"psr-4": {
"modules\": "modules/"
}
},
"config": {
"optimize-autoloader": true,
"platform": {
"php": "7.0"
}
},
"scripts": {
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
]
}
}
When I perform a composer create-project vendor/package ., it only installs the given requirements as specified in the composer.json file.
In case I want the latest dependencies, I need to perform a composer update after the install is complete. I wonder if there is another way of installing the latest dependencies with only the composer create-package command.
The inspiration of my bootstrap package is Andrew Welch's craft repo. If I install his repo as documented in the readme, I immediately get the latest dependencies, whilst the dependences specified in the composer.json file are older versions.
Is there some setting I'm forgetting that takes care of this?
composer-php
add a comment |
up vote
0
down vote
favorite
I have private repository in which we have a composer.json file.
{
"name": "vendor/package",
"version": "1.1.0",
"type": "project",
"require": {
"craftcms/cms": "^3.0.0",
"ether/splash": "^v3.0.2",
"ether/simplemap": "^v3.3.4",
"aelvan/imager": "^v2.1.1",
"vlucas/phpdotenv": "^2.4.0",
"craftcms/redactor": "^2.1.6",
"craftcms/mandrill": "^1.2.0",
"sebastianlenz/linkfield": "^1.0.15",
"solspace/craft3-freeform": "^2.4.1",
"nystudio107/craft-minify": "^1.2.9",
"nystudio107/craft-seomatic": "^3.1.26",
"pieterxjan/slack-error-notifications": "^1.0"
},
"autoload": {
"psr-4": {
"modules\": "modules/"
}
},
"config": {
"optimize-autoloader": true,
"platform": {
"php": "7.0"
}
},
"scripts": {
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
]
}
}
When I perform a composer create-project vendor/package ., it only installs the given requirements as specified in the composer.json file.
In case I want the latest dependencies, I need to perform a composer update after the install is complete. I wonder if there is another way of installing the latest dependencies with only the composer create-package command.
The inspiration of my bootstrap package is Andrew Welch's craft repo. If I install his repo as documented in the readme, I immediately get the latest dependencies, whilst the dependences specified in the composer.json file are older versions.
Is there some setting I'm forgetting that takes care of this?
composer-php
Do you havecomposer.lockin this repo?
– rob006
Nov 19 at 9:57
@rob006 No, there is no lockfile in the repository.
– PieterxJan
Nov 19 at 10:58
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have private repository in which we have a composer.json file.
{
"name": "vendor/package",
"version": "1.1.0",
"type": "project",
"require": {
"craftcms/cms": "^3.0.0",
"ether/splash": "^v3.0.2",
"ether/simplemap": "^v3.3.4",
"aelvan/imager": "^v2.1.1",
"vlucas/phpdotenv": "^2.4.0",
"craftcms/redactor": "^2.1.6",
"craftcms/mandrill": "^1.2.0",
"sebastianlenz/linkfield": "^1.0.15",
"solspace/craft3-freeform": "^2.4.1",
"nystudio107/craft-minify": "^1.2.9",
"nystudio107/craft-seomatic": "^3.1.26",
"pieterxjan/slack-error-notifications": "^1.0"
},
"autoload": {
"psr-4": {
"modules\": "modules/"
}
},
"config": {
"optimize-autoloader": true,
"platform": {
"php": "7.0"
}
},
"scripts": {
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
]
}
}
When I perform a composer create-project vendor/package ., it only installs the given requirements as specified in the composer.json file.
In case I want the latest dependencies, I need to perform a composer update after the install is complete. I wonder if there is another way of installing the latest dependencies with only the composer create-package command.
The inspiration of my bootstrap package is Andrew Welch's craft repo. If I install his repo as documented in the readme, I immediately get the latest dependencies, whilst the dependences specified in the composer.json file are older versions.
Is there some setting I'm forgetting that takes care of this?
composer-php
I have private repository in which we have a composer.json file.
{
"name": "vendor/package",
"version": "1.1.0",
"type": "project",
"require": {
"craftcms/cms": "^3.0.0",
"ether/splash": "^v3.0.2",
"ether/simplemap": "^v3.3.4",
"aelvan/imager": "^v2.1.1",
"vlucas/phpdotenv": "^2.4.0",
"craftcms/redactor": "^2.1.6",
"craftcms/mandrill": "^1.2.0",
"sebastianlenz/linkfield": "^1.0.15",
"solspace/craft3-freeform": "^2.4.1",
"nystudio107/craft-minify": "^1.2.9",
"nystudio107/craft-seomatic": "^3.1.26",
"pieterxjan/slack-error-notifications": "^1.0"
},
"autoload": {
"psr-4": {
"modules\": "modules/"
}
},
"config": {
"optimize-autoloader": true,
"platform": {
"php": "7.0"
}
},
"scripts": {
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
]
}
}
When I perform a composer create-project vendor/package ., it only installs the given requirements as specified in the composer.json file.
In case I want the latest dependencies, I need to perform a composer update after the install is complete. I wonder if there is another way of installing the latest dependencies with only the composer create-package command.
The inspiration of my bootstrap package is Andrew Welch's craft repo. If I install his repo as documented in the readme, I immediately get the latest dependencies, whilst the dependences specified in the composer.json file are older versions.
Is there some setting I'm forgetting that takes care of this?
composer-php
composer-php
asked Nov 19 at 8:18
PieterxJan
1
1
Do you havecomposer.lockin this repo?
– rob006
Nov 19 at 9:57
@rob006 No, there is no lockfile in the repository.
– PieterxJan
Nov 19 at 10:58
add a comment |
Do you havecomposer.lockin this repo?
– rob006
Nov 19 at 9:57
@rob006 No, there is no lockfile in the repository.
– PieterxJan
Nov 19 at 10:58
Do you have
composer.lock in this repo?– rob006
Nov 19 at 9:57
Do you have
composer.lock in this repo?– rob006
Nov 19 at 9:57
@rob006 No, there is no lockfile in the repository.
– PieterxJan
Nov 19 at 10:58
@rob006 No, there is no lockfile in the repository.
– PieterxJan
Nov 19 at 10:58
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370702%2finstall-latest-composer-dependencies%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you have
composer.lockin this repo?– rob006
Nov 19 at 9:57
@rob006 No, there is no lockfile in the repository.
– PieterxJan
Nov 19 at 10:58