-
Notifications
You must be signed in to change notification settings - Fork 687
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
[feature]: Debugging Reporter #2910
Conversation
|
Signed-off-by: sirugh <rugh@adobe.com>
Signed-off-by: sirugh <rugh@adobe.com>
Love it ❤️ Can you also add a feature where the whole output is copied to the clipboard so people can simply paste it into the issue? |
Copy commands differ across operating systems. I figured for now it's easy enough to just ask folks to copy the output of the command into the issue when creating one. |
Ahhh got it. Makes sense. |
Signed-off-by: sirugh <rugh@adobe.com>
.github/ISSUE_TEMPLATE/bug_report.md
Outdated
If applicable, add screenshots to help explain your problem. | ||
|
||
**Additional context** | ||
Add any other context about the problem here. | ||
|
||
Paste the output of `yarn build:report`, and any other context about the problem, here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
} | ||
|
||
function inspectBuildEnv() { | ||
const osVersion = os.version(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, you're right! Our monorepo package.json requires at least 10, but if this doesn't work in 10 we need a fall back (upgrading to minimum 12 is definitely out of scope).
|
||
function inspectBuildEnv() { | ||
const osVersion = os.version(); | ||
const nodeVersion = process.version(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure of this API? I checked the node docs and realized process.version
is a string, not a function.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another good catch. I wonder how I got this to work. Maybe I had it written when I ran it for the screenshot and forgot to push? 🤷 Thanks for fixing :)
Found it Our CICD must be on a version of Node that does not support |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved again - we skip the os.version
check if we aren't on >= node 13.
@sirugh @revanth0212 Have some queries with respect this report tool code dependency with rest of pwa-studio.
|
Haha no, but it is easier to make it a utility of buildpack than a random extension. Also the initial ticket/request suggested it be a buildpack utility, which is why I went that direction. Stop trying to throw in scope @dpatil-magento!
Try it :P |
QA Approved. |
Description
This feature/hackathon project should make it easier for folks to provide debugging info about their Magento/PWA Studio system.
I was not able to access extension or target usage info. I wasn't sure what the optimal way to do this was. Perhaps there is some tooling we have already written that exposes it.
Related Issue
Closes PWA-1091.
Acceptance
Verification Stakeholders
Specification
Verification Steps
DEBUG_PROJECT_CREATION=1 ../pwa-studio/packages/create-pwa/bin/create-pwa
yarn install
andyarn build:report
Screenshots / Screen Captures (if appropriate)
Checklist