J Rob Gant

Based on the [AWS CLI documentation](https://docs.aws.amazon.com/amplify/latest/userguide/update-website-deployed-from-s3.html) I have a work-around until manual deploys are supported: ```tf resource "null_resource" "deploy_from_s3" { triggers = { file_hashes = jsonencode({ for fn in fileset("${path.root}/dist",...

@cirnatdan what do you mean? A deployment is a process. When it is over the site is deployed forever.

When `source_url` changes, trigger a deployment. That doesn't need be a resource, it just needs to be an action.

What is the status of this work? Is it still being considered or will it not be added at this time?

Very annoying that this schematic overwrites the default angular ones.

@jennifer-shehane can someone please look into this issue? I never would have expected Cypress to completely replace all of my tests in my component schematic. That and not actually updating...

This is still a problem in 2025 using `@stylistic/[email protected]` ``` warning Caution: `stylistic` also has a named export `configs`. Check if you meant to write `import {configs} from '@stylistic/eslint-plugin'` instead...

What is the (complete) output of `npm list punycode`? What is the (complete) output of `ng version`? Because for me, `punycode` doesn't appear to be a dependency of `@angular/fire`.

See: * https://github.com/angular/angularfire/blob/main/docs/zones.md#logging * https://github.com/angular/angularfire/issues/3607 * https://github.com/angular/angularfire/issues/3605 * https://github.com/angular/angularfire/issues/3611 * https://github.com/angular/angularfire/issues/3614 * https://github.com/angular/angularfire/issues/3621 And https://github.com/rgant/brainfry/blob/35b5607c2e9186f5a46ff7adfae486cd1737d8df/src/app/core/firebase-app.provider.ts#L6. IMO, if you are using the modular syntax these messages aren't useful so I have...

Also I'll re-ask for documentation of configuration when using a flat config.