-
Notifications
You must be signed in to change notification settings - Fork 142
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
Upgrade resolver tests #1321
Upgrade resolver tests #1321
Conversation
…enamed package" test
changed `<MyAddon$Thing />` to `<MyAddon@Thing />` to match test description
Looking good, thanks. |
revert change to test from @ to $
…reference inside node_modules" test
…a renamed package" test
…ates no warning" test
… no warning" test
…ultiple levelsl" test
@ef4 have gone through all skipped tests in the resolver.tests.ts file there are several commits that look like they have the expected outcome (from the test perspective) but I have doubts about intended output of the transform step - I've marked such commits with an * at the beginning so they are easy to spot looking for input on next steps / criteria to land this |
@ef4 here are a couple of them to make sure I'm doing this correctly, the rest will follow