-
Notifications
You must be signed in to change notification settings - Fork 18
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
add import json tests #247
Conversation
the main error blocking this branch is reproduced here https://github.com/iambumblehead/nodejs-import-attributes-repro |
Possibly, if the issue were reported upstream now, it would be de-prioritized and forgotten because of the experimental state of import attributes. Therefore, it might be better to wait and create an issue later when import attributes are more stable. |
This PR enables mocking of imported json files and can hang out here for a few weeks. A commented-out test here fails, because of an acknowledged bug at nodejs upstream. @koshic @Swivelgames if you are available, please review and give your opinion. |
ce2e7e2
to
c5eb9ea
Compare
the test only passes in node 21 upstream issue was resolved but maybe the solution has not been ported to node 18 or 20 yet |
bdf3eab
to
913c105
Compare
…tream issue is resolved those
cacdfa4
to
97993ad
Compare
re #246
On first implementation, there is an issue. When multiple tests are added around this feature, they fail. Nodejs returns only the first-resolved json result to many callers., even though each mocked-json is requested through its own unique uri.