-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
fix: client-side simulation does not work in test #157
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@chungweileong94 is attempting to deploy a commit to the t3-oss Team on Vercel. A member of the Team first needs to authorize it. |
@@ -336,17 +336,19 @@ describe("shared can be accessed on both server and client", () => { | |||
FOO_BAR: "foo", | |||
}; | |||
|
|||
const env = createEnv({ |
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.
Previously we called createEnv
before "simulate" the window
object below, which mean we already get env
in server mode.
Nothing change to the test result, but at least the client-side simulation is fixed.
}); | ||
const env = lazyCreateEnv(); | ||
|
||
expect(() => env.BAR).toThrowErrorMatchingInlineSnapshot( |
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.
Technically we don't have to check this in this test case, but I figure why not🤷
fix #156