The build process is open source, as are any adapters we use to help align vanilla code to best practices. Some stuff is magic (e.g. the FIREBASE_CONFIG env being automatically injected), but I’d hardly call that a risk of lock-in.
Awesome stuff, I think it’s a super useful tool you’ve built and I’ll definitely be using it, in my next project most likely. I’ll check out those links :) cheers
Comments
That’s awesome as someone that builds NextJs fullstack.
I’ve really enjoyed using Firebase so far as the backend for my in-development chrome extension.
Using Firebase Auth, Cloud Functions, Hosting, Firestore, and the local emulator.
Now if I ever make a NextJs web app, I’d probably use Firebase app hosting
Be careful of vendor lock-in. Especially when it comes to Google.
The build process is open source, as are any adapters we use to help align vanilla code to best practices. Some stuff is magic (e.g. the FIREBASE_CONFIG env being automatically injected), but I’d hardly call that a risk of lock-in.
Are you a Google dev? I think I’m doing crazy things with chrome extensions, Firebase, and LLMs if you ever need a developer voice for these products.
Yes, I’m the engineering lead of Firebase App Hosting. If you have anything you want to talk about, inlined.dev has all the places you can find me.
Awesome stuff, I think it’s a super useful tool you’ve built and I’ll definitely be using it, in my next project most likely. I’ll check out those links :) cheers
That’s true, I’m also versed in Azure as a backup