Silly, slightly pointless, question. Should `sst-e...
# help
r
Silly, slightly pointless, question. Should
sst-env.d.ts
be ignored from git? Curious what others do.
t
it shouldn't be ignored right now because we don't have a way to programmatically generate it
if your build process is
Copy code
1. npm install
2. typecheck
3. sst deploy
It might fail #2 if it's not checked in
strictly speaking this isn't great but practically fine for now
r
Alright thats good to know. Curious why deploy wouldnt re-gen it?
oh wait i see, it does regen it... but it happened to late haha
t
yeah the other nice thing about checking it in is there is a nice history in git. Less useful for something simple like sst-env.d.ts but more useful for graphql schema generation
in the future I think we should support
Copy code
1. npm install
2. sst build
3. typecheck
4. sst deploy-with-result-from-2
j
^ that would be amazing! Especially when just deploying it to other environments, would be good to keep the same codes but maybe replace all ENV Vars.
r
yeah that makes sense
sst deploy --cached
or something. Could also use postinstall hook to get that build 🤷‍♂️