Brett Fieber
05/09/2022, 10:08 PMyarn build twice?
...
info "esbuild-windows-arm64@0.14.38" is an optional dependency and failed compatibility check. Excluding it from installation.
info esbuild-windows-arm64@0.14.38: The CPU architecture "x64" is incompatible with this module.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
> frontend@0.1.0 build
> cross-env NODE_ENV=production yarn run build:styles && tsc && vite build
$ cross-env NODE_ENV=production postcss src/styles/index.css -o public/styles.css --config ./
Source path: /tmp/seed/source/frontend/src/styles/index.css
Setting up new context...
Finding changed files: 3.836ms
...
removed for brevity
...
CDK_CLI_VERSION: '2.15.0'
}
Building static site frontend
> frontend@0.1.0 prebuild
> yarn
[1/4] Resolving packages...
success Already up-to-date.
> frontend@0.1.0 build
> cross-env NODE_ENV=production yarn run build:styles && tsc && vite build
$ cross-env NODE_ENV=production postcss src/styles/index.css -o public/styles.css --config ./
Source path: /tmp/seed/source/frontend/src/styles/index.css
Setting up new context...
Finding changed files: 4.027ms
Reading changed files: 413.2ms
...Brett Fieber
05/11/2022, 9:42 PMFrank
cdk.context.json file? If it is, make sure the file is commited to git.Frank
cdk.context.json. If the cache file does not exist, CDK would build once, write to the cache, and builds again.Frank
git diff cdk.context.json inside before_deploy. And commit the changes to git.Frank
Brett Fieber
05/12/2022, 1:48 AM.gitignore because I though it would be unique to each environment.
How do you handle when you may deploy the service to multiple environments?