Skip to content

Conversation

rafaelstz
Copy link
Member

Many devs in my team and community report issues installing PWA Studio in their local environments. The issues are mainly related to DNS, Node or Yarn version, ports in use, etc.
Adding devcontainer to Venia Concept will make it much easier to start developing after yarn create @magento/pwa.

It has Node 18 LTS and a small Nodejs Docker image made exclusively for VSCode and CodeSpace.

The next step would be adding guidance on DevDocs. I will do it when the PR is merged.

Screenshot 2023-09-20 135022

@pwa-studio-bot
Copy link
Collaborator

pwa-studio-bot commented Sep 20, 2023

Fails
🚫

node failed.

🚫 A version label is required. A maintainer must add one.
🚫

Unable to build scaffolded project.

yarn build

within a scaffolded project directory failed.
Learn more about Scaffolding at https://magento.github.io/pwa-studio/pwa-buildpack/scaffolding/.

🚫

No linked issue found. Please link a relevant open issue by adding the text "closes #<issue_number>" or "closes JIRA-<issue_number>" in your PR.

🚫 Missing "Verification Steps" section. Please add it back, with detail.
🚫 Missing "Description" section. Please add it back, with detail.
Messages
📖 DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed).
📖

Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.

Log

ERROR ON TASK: scaffoldingSucceeds


Error:  Danger had errors running. See message(s) above for more details.
danger-results://tmp/danger-results.json

If your PR is missing information, check against the original template here. At a minimum you must have the section headers from the template and provide some information in each section.

Generated by 🚫 dangerJS against aec3ad9

@glo82145
Copy link
Collaborator

glo82145 commented Aug 11, 2025

As this PR is too old we are closing this PR. If you still need to integrate these changes please create a community issue and we will reopen this PR and merge it.

@glo82145 glo82145 closed this Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants