amplify-backend
amplify-backend copied to clipboard
aws-amplify
Home to all tools related to Amplify's code-first DX (Gen 2) for building fullstack apps on AWS
Follow up on https://github.com/aws-amplify/amplify-backend/issues/655 where initial version was developed. TODO: 1. Further expansion to cover: 1. inheritance 2. exported consts 3. See TODOs in https://github.com/aws-amplify/amplify-backend/blob/main/scripts/components/api-changes-validator/api_usage_statements_generators.ts 2. Integration with semver diffs/changeset....
### Description Our e2e tests can only be run on branches in the repo because the e2e tests have access to our test AWS account. If a PR from a...
Emit a CW metric in our sandbox e2e tests to track sandbox deployment time trends. We should be able to see if we are trending up or down even if...
### Environment information ```plain text n/a ``` ### Description We had to introduce execa v5 to [packages/plugin-types/src/package_manager_controller.ts](https://github.com/aws-amplify/amplify-backend/pull/960/files/8b4619f874e6ddc7c2d29ece702b3afe6c835c5a#diff-2f030b9491fc33db8d08bd86685132c7fb41ba6f49250f21ff38998877d43da3), because it's the latest execa version that supports commonjs. ref: https://github.com/sindresorhus/execa/issues/489#issuecomment-1109983390 This change...
From https://github.com/aws-amplify/amplify-backend/pull/960/files#r1473293291 . We should add configuration knob to `DependenciesValidator` to control which packages are exempt from consistency check.
See discussion on https://github.com/aws-amplify/samsara-cli/pull/286 Some of our packages need to be importable by CJS which requires special package.json config
### Is this related to a new or existing framework? _No response_ ### Is this related to a new or existing API? Authentication, Storage ### Is this related to another...
Follow up from https://github.com/aws-amplify/amplify-backend/pull/594 . Now that we truncate and hash inputs for stack naming purposes we should also stash unmodified inputs somewhere in stack metadata, so that information is...
## Problem follow-up to https://github.com/aws-amplify/amplify-backend/pull/709 Enforces consistent type imports and exports. This can help prevent errors such as https://typescript.tv/errors/#ts2742 when consuming the libraries with pnpm or npm's "linked" install strategy....
### Environment information ```plain text n/a ``` ### Description Error like mentioned in https://github.com/aws-amplify/amplify-backend/pull/906 should be caught by linter.
Metadata
Owner
Metadata
Home to all tools related to Amplify's code-first DX (Gen 2) for building fullstack apps on AWS