✅ - Artifact directory doesn't exist | AWS Amplify | Page 1

silent karma Jan 19, 2024, 9:28 PM

#

amplify.yml

version: 1
applications:
    -
        backend:
            phases:
                build:
                    commands: ['nvm use 18', 'npm i --no-frozen-lockfile', 'npx amplify pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID']
        frontend:
            phases:
                preBuild:
                    commands: ['npx pnpm install']
                build:
                    commands: ['npx turbo run build --filter=webapp']
            artifacts:
                baseDirectory: apps/webapp/.next
                files:
                    - '**/*'
            cache:
                paths:
                    - 'node_modules/**/*'
            buildPath: /
        appRoot: apps/webapp

what am I doing wrong?

#

Next.js app with no distDir specified (.next is default)

#

even specifying a distDir yields same results

worthy adder Jan 19, 2024, 9:50 PM

#

@leaden geyser - you able to look?

silent karma Jan 19, 2024, 9:54 PM

#

also, not sure if it makes a difference, but I changed the "npm ci" command to "npm i --no-frozen-lockfile" because pnpm was complaining about the package.json of my nextapp package being out of sync with the root project's package-lock.json. otherwise this is the amplify.yml generated by the amplify web console.

spice anvil Jan 19, 2024, 10:11 PM

#

👋 is this for a pnpm monorepo?

silent karma Jan 19, 2024, 10:17 PM

#

yes indeed

#

.npmrc is in project root with node-linker = hoisted

spice anvil Jan 19, 2024, 10:24 PM

#

is this the only frontend app in your monorepo that you want to host?

silent karma Jan 19, 2024, 10:25 PM

#

yes

spice anvil Jan 19, 2024, 10:31 PM

#

can you try this?

version: 1
backend:
  phases:
    build:
      commands:
        - nvm use 18
        # enable corepack to autoresolve pnpm https://nodejs.org/api/corepack.html
        - corepack enable
        - pnpm install
        - pnpm amplify pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID
  cache:
    paths:
    - $(pnpm store path)
frontend:
  phases:
    build:
      commands: 
        - pnpm turbo run build --filter=webapp
  artifacts:
    baseDirectory: apps/webapp/.next
    files:
      - '**/*'
  cache:
    paths:
    - '**/.turbo'

silent karma Jan 19, 2024, 10:32 PM

#

building now

spice anvil Jan 19, 2024, 10:33 PM

#

and what's neat about pnpm monorepo's is using the deploy command. you can specify a package filter and out directory on deploy, and pnpm will build the necessary workspace dependencies and load them into a new dependency store in the chosen out dir
https://github.com/josefaidt/amplify-hosting-monorepo-with-pnpm/blob/main/amplify.yml

silent karma Jan 19, 2024, 10:34 PM

#

!!! CustomerError: Monorepo spec provided without "applications" key

silent karma Jan 19, 2024, 10:35 PM

#

spice anvil and what's neat about pnpm monorepo's is using the `deploy` command. you can spe...

this is interesting. im checking this repo out now to make sure ive got everything in order

spice anvil Jan 19, 2024, 10:36 PM

#

silent karma > !!! CustomerError: Monorepo spec provided without "applications" key

hmm let me see where we can turn off monorepo

spice anvil Jan 19, 2024, 10:39 PM

#

silent karma .npmrc is in project root with node-linker = hoisted

you can also remove this config setting if using pnpm deploy

silent karma Jan 19, 2024, 10:49 PM

#

should i be using pnpm deploy here?

spice anvil Jan 19, 2024, 10:51 PM

#

just updated that yaml for caching the turbo builds

spice anvil Jan 19, 2024, 10:52 PM

#

silent karma should i be using pnpm deploy here?

either pnpm or turbo are fine. they have slightly different approaches to building monorepo apps

#

with pnpm deploy you won't need to worry about hoisting deps because it'll build to a single directory

modern gale Jan 19, 2024, 10:55 PM

#

spice anvil either pnpm or turbo are fine. they have slightly different approaches to buildi...

Hi Josef What about nx ? Is it work too ?

silent karma Jan 19, 2024, 10:55 PM

#

spice anvil just updated that yaml for caching the turbo builds

!!! CustomerError: Unable to parse build spec: unidentified alias "*/.turbo"

spice anvil Jan 19, 2024, 10:56 PM

#

silent karma > !!! CustomerError: Unable to parse build spec: unidentified alias "*/.turbo"

ah sorry that was missing quotes

silent karma Jan 19, 2024, 10:56 PM

#

i figured

spice anvil Jan 19, 2024, 10:56 PM

#

modern gale Hi Josef What about nx ? Is it work too ?

I believe a few folks in the server use nx!

silent karma Jan 19, 2024, 10:57 PM

#

silent karma > !!! CustomerError: Monorepo spec provided without "applications" key

same response

modern gale Jan 19, 2024, 10:59 PM

#

spice anvil I believe a few folks in the server use nx!

Thank you

spice anvil Jan 19, 2024, 11:06 PM

#

silent karma same response

do you have the AMPLIFY_MONOREPO_APP_ROOT environment variable set by chance?

silent karma Jan 19, 2024, 11:08 PM

#

spice anvil do you have the `AMPLIFY_MONOREPO_APP_ROOT` environment variable set by chance?

yes

#

do i need to remove them?

spice anvil Jan 19, 2024, 11:09 PM

#

silent karma yes

can you remove it and try rebuilding?

silent karma Jan 19, 2024, 11:09 PM

#

ok

silent karma Jan 19, 2024, 11:44 PM

#

spice anvil can you remove it and try rebuilding?

now my backend isnt being recognized

#

 [31mAmplify Backend not found in /codebuild/output/src659560591/src/v2. Amplify Backend must be defined in amplify/backend.(ts|js|cjs|mjs)[0m

#

apps/webapp is a app router next app with /amplify directory bootstrapped with gen 2

#

i believe the error would be different if the /amplify folder couldnt be found correct? i remember seeing an error associated with amplify project not found or something along those lines.

somber pecan Jan 20, 2024, 12:05 AM

#

That repo sample is nice, thanks @spice anvil. What would be the difference with two frontend apps?

spice anvil Jan 20, 2024, 12:25 AM

#

silent karma i believe the error would be different if the /amplify folder couldnt be found c...

ah yes, you can use --filter to run it on your workspace. I think it would be something like

pnpm --filter ./apps/webapp exec amplify pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID

silent karma Jan 20, 2024, 12:25 AM

#

spice anvil ah yes, you can use `--filter` to run it on your workspace. I think it would be ...

ahhh

spice anvil Jan 20, 2024, 12:26 AM

#

somber pecan That repo sample is nice, thanks <@143912968529117185>. What would be the differ...

it should be relatively similar! you can likely set the appRoot to the workspace root and use the same approach to build and deploy

somber pecan Jan 20, 2024, 12:30 AM

#

spice anvil it should be relatively similar! you can likely set the `appRoot` to the workspa...

Got it, that would mean having two amplify.yaml in each app, like apps/app1/amplify.yml, and the appRoot set to . 🤔 . I'll play around with that, thanks!

spice anvil Jan 20, 2024, 12:31 AM

#

somber pecan Got it, that would mean having two `amplify.yaml` in each app, like `apps/app1/a...

the yaml file should live at the root of your repo, and you can define multiple applications (both with the appRoot set to .)

somber pecan Jan 20, 2024, 12:31 AM

#

spice anvil the yaml file should live at the root of your repo, and you can define multiple ...

Oh, so instead of calling them frontend, I can simply call them two different names and have the settings there

#

Well, I imagine I would need to use the Amplify App name

silent karma Jan 20, 2024, 12:52 AM

#

#

:///

#

nevermind

#

i forgot to push my next.config with updated distDir. had a mini heart attack lol

silent karma Jan 20, 2024, 1:21 AM

#

im deployed with no errors, though the domain in amplify console is returning a 404

silent karma Jan 20, 2024, 4:30 AM

#

sorry for late ping @spice anvil, im getting 404 because platform is being configured for "WEB". how do I change the platform / specify it during build?

spice anvil Jan 20, 2024, 6:55 PM

#

silent karma sorry for late ping <@143912968529117185>, im getting 404 because platform is be...

you can use the AWS CLI to set it to WEB_COMPUTE https://docs.aws.amazon.com/cli/latest/reference/amplify/update-app.html#options

#

aws amplify update-app --app-id <your-app-id> --platform WEB_COMPUTE

silent karma Jan 20, 2024, 7:45 PM

#

spice anvil you can use the AWS CLI to set it to WEB_COMPUTE https://docs.aws.amazon.com/cli...

i was passing it in quote

#

kek kek

silent karma Jan 20, 2024, 8:34 PM

#

spice anvil you can use the AWS CLI to set it to WEB_COMPUTE https://docs.aws.amazon.com/cli...

this is failing without an error msg

silent karma Jan 20, 2024, 8:57 PM

#

was because of aws prefixing the command. i am now getting permissions errors on aws.
An error occurred (AccessDeniedException) when calling the UpdateApp operation: User: ...... is not authorized to perform: amplify:UpdateApp on resource <Amplify_ARN>

#

I think im going to just use SST / OpenNext. I cant really afford to spend any more time figuring this out, plus i would probably have another couple of days of debugging to do to get another dev up to speed. Ill revisit when things are a bit further along. Thanks for the assistance @spice anvil you've been amazing.

spice anvil Jan 21, 2024, 2:22 AM

#

silent karma was because of aws prefixing the command. i am now getting permissions errors on...

ah you'll want to go into the iam console and add this permission as an inline policy for the user you're using locally

idle krakenBOT Mar 11, 2024, 2:05 PM

#

✅ - Artifact directory doesn't exist

#✅ - Artifact directory doesn't exist