-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Issues with windows 11 #19
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Stepping thorugh there is this bit of lines
within leverages this code from glob:
from which in turn invokes: the Glob constructor:
but the opts isn't a callback like the code in restest.mjs would indicate. further the walk object on that function just returns those files... also glob documentation https://github.com/isaacs/node-glob shows the glob function returning a promise not callbacks |
Changing the code in https://github.com/bloodyowl/rescript-test/blob/main/bin/retest.mjs from
to
looks to fix the issue. @bloodyowl happy to issue a PR if this approach looks reasonable |
Hello I am working on Windows 11 (my personal laptop) with ReScript 11. I am looking to learn more about ReScript and want to explore testing. This framework looks to be all i need, but it doesn't seem to be working correctly
node ./node_modules/rescript-test/bin/retest.mjs
node ./node_modules/rescript-test/bin/retest.mjs tests/entities/parser/test_parser.bs.js
node ./node_modules/rescript-test/bin/retest.mjs tests/entities/parser/*.bs.js
node ./node_modules/rescript-test/bin/retest.mjs tests/entities/**/test_parser.bs.js
I am a hobbiest at this point in my career (software executive) and have some rusty skills - so I may be missing something obviuos. I have added some debugging into
retest.mjs
and I don't think theglob
nodeback
is returning or isn't returning and the promises are not properly waited upon. The script does exit which indicates that the promises are not being waited on - but the code looks cool correct...Logging in the event that I am missing something obvious. Will update if I uncover anything else
The text was updated successfully, but these errors were encountered: