-
Notifications
You must be signed in to change notification settings - Fork 88
Feat/tinny standalone #722
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
Conversation
…na distrupt the tinny env init process
| }, | ||
| }; | ||
|
|
||
| export const tinnyTests = { |
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.
Can we import this huge json into test.ts:testConfig.tests to avoid the huge imports block there?
| await bundle(); | ||
| console.log(`[build.mjs] 🚀 Build time: ${Date.now() - start}ms`); | ||
| } catch (error) { | ||
| console.error(`[build.mjs] ❌ Build failed:`, error); |
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.
This will hide the error. We can add a process.exit(1) to notify caller
|
This is already included in naga |
WHAT
This PR takes the E2E tests I’ve already built for the SDK and turns them into a reusable package. Internal members asked for this so they can use it to test custom networks and tie it into observability projects to keep an eye on service health. This makes the tests more flexible and useful for everyone.
COMMANDS
To build
To Publish (Have to manually update package version)
Package usage
Overview
See this repo for more details