Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@wordpress/env 9.0.0 Error on first build. #57243

Closed
tKakazu opened this issue Dec 20, 2023 · 3 comments
Closed

@wordpress/env 9.0.0 Error on first build. #57243

tKakazu opened this issue Dec 20, 2023 · 3 comments
Labels
Needs Testing Needs further testing to be confirmed. [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. [Tool] Env /packages/env [Type] Bug An existing feature does not function as intended

Comments

@tKakazu
Copy link

tKakazu commented Dec 20, 2023

Description

What?

Before composer require phpunit, create and authorize the "/.composer" directory.
Change line 250 of 'packages/env/lib/init-config.js' like this.

USER $HOST_UID:$HOST_GID
ENV PATH="\${PATH}:/home/$HOST_USERNAME/.composer/vendor/bin"

USER root
RUN mkdir -p /.composer && chmod -R 775 /.composer
RUN composer global require --dev phpunit/phpunit:"^5.7.21 || ^6.0 || ^7.0 || ^8.0 || ^9.0 || ^10.0"

Why?

Prevents this error from occurring.
/.composer does not exist and could not be created:

I was unable to submit the request due to a pull request permission error.
I apologize for the inconvenience and thank you for your understanding.

Step reproduction instructions

Run 'env WP_ENV_HOME=./new-wordpress wp-env start' in the new directory

@tKakazu tKakazu added the [Type] Bug An existing feature does not function as intended label Dec 20, 2023
@tKakazu
Copy link
Author

tKakazu commented Dec 20, 2023

I forgot to add the "[Package] Env" label.

@t-hamano t-hamano added Needs Testing Needs further testing to be confirmed. [Tool] Env /packages/env labels Dec 20, 2023
Copy link

Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.

@github-actions github-actions bot added the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label Jan 20, 2024
@swissspidy swissspidy added the [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed label Jan 25, 2024
@swissspidy
Copy link
Member

I think this is a duplicate of #51419

@swissspidy swissspidy closed this as not planned Won't fix, can't repro, duplicate, stale Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Testing Needs further testing to be confirmed. [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. [Tool] Env /packages/env [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

3 participants