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
Update Windows instructions in README.md #4184
Conversation
* Update readme for windows I had a tough time getting this working on windows. Updated readme to help.
Microsoft Edge's current set of tests for an ECMAScript6 Modules implementation via the script element (<script type="module">).
LGTM! |
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.
Thanks—glad we’re getting more help for people to get their wpt environment set up on Windows successfully. See other comments for minor nits.
Leave the default install settings so Python will be installed to the c:\python2x directory. | ||
|
||
Be sure to add that directory to your `%Path%` | ||
[Environment Variable](http://www.computerhope.com/issues/ch000549.htm). |
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.
The %Path%
syntax is Windows-specific, right? And the http://www.computerhope.com/issues/ch000549.htm info is also Windows-specific. So it seems like this should be moved to that Windows Notes section.
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.
Thanks for that. I've moved that sentence to the Windows Notes section now.
Add ECMAScript 6 Modules test cases
Moving the PATH information to Windows notes section.
@thejohnjansen seems the “Add ECMAScript 6 Modules test cases” change (e6fdc7d / 360d873) got inadvertently committed to the branch. I guess that happened because the PR was made from the To prevent things like this, it’s always better to create a branch in your wpt fork for each PR and commit there instead of If you want, I can fix this so we can merge this PR, but it means I would need to force-push to the https://github.com/MicrosoftEdge/web-platform-tests After I did that and merge this PR you’d need to pull from https://github.com/MicrosoftEdge/web-platform-tests and then re-merge that “ES6 Modules test cases” change to If you prefer to do it yourself (rather me being the one doing the force-push), what you’d need to is:
After that we merge this PR but you’d still need to pull from https://github.com/MicrosoftEdge/web-platform-tests and then re-merge that “ES6 Modules test cases” change to |
hey @sideshowbarker, thanks for the detailed summary. I tried to do the commands myself, but I got an error when I ran git push -f |
PS: I cannot believe I didn't create a new branch and then complicated this PR like that. Embarassing. |
@thejohnjansen no worries—I just went ahead and merged it on the command from my local copy of the branch |
This is part of #3776. (Ignore me. I'm doing housekeeping.) |
I had a tough time getting this working on windows. Updated readme to
help.