Yo! <@U01JVDKASAC> - spotted today that that if I ...
# guide
t
Yo! @Frank - spotted today that that if I follow the sst guide (with default language - javascript), when I try to deploy the whole thing for the first time i get this (after running npx sst start): Cannot find app handler. Make sure to add a "stacks/index.ts" file.
@Jay / @Frank / @thdxr - something you're aware of? or am I a muppet and I'm doing something terribly wrong?
t
Ah sorry about this, I had just updated the examples make our default folder
lib
->
stacks
I think the docs may not have been updated
How did you bootstrap your application?
t
Following the guide, gimme a sec
t
I figured it out - I accidentally made everything look for a
.ts
file instead of a
.js
file - my Typescript evangelism has gone too far. Fixing it now
t
Well, to be honest- as soon as I realized the project is full of js files - I switched to ts version as well - but still decided to raise it - so that other people don't fall into the trap 😄
and you know - maybe you wanna make ts version the default one 😄 (when no parameters are passed)
after switching to Typescript I'm struggling to find like literally any reason why you would want to use vanilla JS 😄
strong typing has saved me from ~1 billion bugs in the last few months 😄
t
I'm definitely on the extreme typescript side and I like doing weird things with types but I also get why people sometimes don't want to deal with the toolchain complexity (building, watching, etc)
t
@thdxr - I tested the latest release - and there is still an issue
t
yeah I found it lol
t
When I inspect the folder structure after running npx create-serverless-stack@latest my-app - it creates "lib" folder, instead of "stacks" folder
t
I renamed lib to stacks manually -and works well afterwards - so that's the last missing bit 🙂
t
going too fast
t
Well, price of being awesome is that you sometimes make small mistakes along the way 😄
😉