| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@refack build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1534/pipeline |
Sorry, something went wrong.
|
What is the point of this? Users already opted in by checking the checkbox, and there is plenty of opportunity to stop it before it starts the package installation. |
Sorry, something went wrong.
Pure UX. Even if this doesn't solve the issue, I would strongly suggest we continue iterating on this issue. I'm flagging this as a regression because of all the negative user feedback 🤷♂️ |
Sorry, something went wrong.
|
/CC @nodejs/build-files @nodejs/platform-windows @nodejs/UX ;) |
Sorry, something went wrong.
|
Good point, to make it clear that it's a different thing. Test build: https://nodejs.org/download/test/v12.0.0-test20181108dab27c03ea/ |
Sorry, something went wrong.
Co-Authored-By: refack <refack@gmail.com>
Co-Authored-By: refack <refack@gmail.com>
|
The output MSI |
Sorry, something went wrong.
Sorry, something went wrong.
Also looks to have a whitespace issue between modules, and some tools. |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
An alternative UX idea:
At the end of the installer open the created Shortcut dir, where the users can explicitly call the new Install Additional Tools for Node.js shortcut.
Refs: #22645
Fixes: #23838
Checklist