-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fix development-environment to work for Windows #1791
Conversation
5 similar comments
@ljharb All's set up now, the tests for Windows as well as the tests for WSL run flawlessly now.
Nvm |
Babelnyc
caused some errors on its currently installed version as seen in the AppVeyor history logs.Some key modules of the development-environment have been updated:
nyc
("on the fly"-update in AppVeyor-script)babel
-modulesmocha
Though, applying this PR won't cause any issues when using with older versions ofnodeJS
(unless babel is configured correctly (see below)), after applying this PR, a nodeJS>=8
is required to develop this project.As mentioned this should have no impact to the usage of the module, but to the development of the module which then will be performed with more modern module-versions.
To ensure, the built module also works for NodeJSargon
, setting this option (targets.node
) to the appropriate version-number might be necessary.This PR fixes #1780 and fixes #1781