-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat: implement browser testing #1431
Conversation
…th test validation
…/feat/implement-vitest
…s/fuels-ts into db/feat/implement-vitest
…/feat/implement-vitest
__esModule: true, | ||
...jest.requireActual('child_process'), | ||
})); | ||
vi.mock('child_process', async () => { |
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.
I personally believe the following format is more readable
vi.mock('child_process', async () => ({
__esModule: true,
...await vi. importActual('child_process'),
}));
const initialDependencies: { file: string; contents: string }[] = []; | ||
|
||
/** | ||
* - Needs refactoring |
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.
Todo
.mockResolvedValue({ | ||
chain: {} as ChainInfo, | ||
nodeInfo: {} as NodeInfo, | ||
}); |
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.
@danielbate why has this changees out of curiosity?
Superceded by #1630 |
browser compatibility
#284Buffer
compatibility for browsers #765