You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently usingprocess.env.VITEST in production code to govern whether checks for the existence of fuelup on the user's machine will be done. This environment variable is only defined in our tests. We should remove this in favor of something else, e.g. a flag like pnpm create fuels --skip-fuelup-check. If we were to switch to e.g. bun for testing, the create-fuels tests would fail because the VITEST environment variable isn't defined.
The text was updated successfully, but these errors were encountered:
We are currently using
process.env.VITEST
in production code to govern whether checks for the existence offuelup
on the user's machine will be done. This environment variable is only defined in our tests. We should remove this in favor of something else, e.g. a flag likepnpm create fuels --skip-fuelup-check
. If we were to switch to e.g.bun
for testing, thecreate-fuels
tests would fail because theVITEST
environment variable isn't defined.The text was updated successfully, but these errors were encountered: