Closed nicolas-grekas closed 11 months ago
Thanks for the PR 😍
Define the SYMFONY_ENDPOINT
environment variable:
# On Unix-like (BSD, Linux and macOS)
export SYMFONY_ENDPOINT=https://raw.githubusercontent.com/symfony/recipes/flex/pull-1229/index.json
# On Windows
SET SYMFONY_ENDPOINT=https://raw.githubusercontent.com/symfony/recipes/flex/pull-1229/index.json
Install the package(s) related to this recipe:
composer req 'symfony/flex:^1.16'
composer req 'api-platform/admin-pack:^1.0' 'symfony/webpack-encore-bundle:^2.0'
Don't forget to unset the SYMFONY_ENDPOINT
environment variable when done:
# On Unix-like (BSD, Linux and macOS)
unset SYMFONY_ENDPOINT
# On Windows
SET SYMFONY_ENDPOINT=
In order to help with the review stage, I'm in charge of computing the diff between the various versions of patched recipes. I'm going keep this comment up to date with any updates of the attached patch.
Just for info. I would like to see the demo also move to NPM (package-lock.json): https://github.com/symfony/demo
I'm curious as to why the recommendation was changed from Yarn to NPM. Are there any information?
Back when we started this recommendation (when introducing webpack-encore), yarn was strictly superior to npm, mostly thanks to having a proper lockfile (at that time, npm did not have package-lock.json but only the shrinkwrap mechanism) and being faster. Since then, npm has caught up on those fronts. And it has the big benefit of being installed by default when you install node, which requires 1 less step. Note however that webpack-encore is not dropping support for yarn (it tests compatibility with several package managers) and so you can keep using yarn if you prefer (or pnpm for that matter)
This makes sense. Thanks for your explanation.
/cc @weaverryan @dunglas