James Daniels

Thanks for the feedback, I'll have to stew on this.

In the latest version of the tooling the next.config.js is now optional, so long as next is a top-level dep in your package.json

At the the moment we don’t allow any configuration of the cloud function. We’re thinking through what that would look like. E.g, a yaml file, command line args, etc. Thanks...

As a work around, you can alter the settings of the auto-generated cloud function in the Google Cloud Console.

Integrating custom isn't too bad, at least for basic SPA. Sorry for the lack of documentation—still doing some work here. Basically package.json needs to fulfill the following contract: 1. an...

Feel free to ping my email with any questions [email protected] & I'd be happy to give you an overview of adding a framework and where we're planning on taking our...

Happy to report that dev-mode is now built into the latest generation of the tooling https://firebase.google.com/docs/hosting/nextjs

Do have any custom configuration in your angular.json? Our deploy will attempt to use the production config by default.

FYI @hsubox76 Need to clean up but here's a first pass on an implementation. Any initial thoughts? We've started bashing on it [go/web-frameworks-bug-bash-init-exp](http://go/web-frameworks-bug-bash-init-exp)

This was posted to the public issue but repeating here for visibility. `@google-cloud/firestore` has begun experimenting with a `preferRest` option (`@6.1.0-pre.0`). Folks should give that a spin. I'm sure once...