Closed KenzoBenzo closed 5 months ago
Hey @KenzoBenzo! sorry you're experiencing this and thanks for flagging 😊
I've just tried to recreate with 0.0.47 and haven't been able to (I have intended behaviour you describe above). Just double checking that you toggled google provider with spacebar? Sorry if that comes across as patronizing! Just want to make sure. If so, can you try to force-clean the cache of your package manager or try a new one?
https://github.com/nicoalbanese/kirimase/assets/49612682/6a0f3bb4-7597-4e10-8eb1-5b156d5dcc49
Hey @nicoalbanese — thanks for responding so quickly!
I am using v0.0.46
for reference and potentially did slip without selecting since I'm not seeing the same behavior on a fresh try. Potentially worth making it a required step? Or output info if you didn't select an option before moving on? Certainly not high priority though, will close since it seems like a non-issue.
No problem! happy to hear it's sorted. So it was an intentional decision to not force anyone into one of the four providers but I like your idea to add a confirmation step (like if you don't select an orm). Will add to the list! Thanks 😊
Config File
Describe the bug When initializing with NextAuth and Google, the provider is not added in correctly.
Expected behavior On initialization, after adding environment variables
Additional context A couple of things fix this. Starting with, in the file
utils.ts
:We need to add these two imports
Inside of the array of providers this code needs to be added (if google is selected)
Then in the file
env.mjs
: Two new environment variable checks need to be madeThen finally the default
.env
file needs to contain two more placeholders