@Warwick Grigg u mentioned the domain is not purchased on Route53. is the DNS managed by Route 53? ie. do you have a Hosted Zone in ur Route 53 console with the domain name?

For now, can you give this a quick try: 1. Create a dummy Route 53 hosted zone with the name of ur domain 2. Configure the

customDomain

in

StaticSite

pretending the domain is hosted on Route53

customDomain: {
    domainName: "<http://domain.com|domain.com>",
    certificate: Certificate.fromCertificateArn(this, "MyCert", certArn),
  },

This should actually work.

(you can remove this after StaticSite supports non-Route 53 domains)

And yeah, let’s add some tests for this use case.

@Frank I followed the guide (but first I installed yarn, npm install -g yarn) but I've hit a snag: on yarn test test/StaticSite.test.ts, I get "Cannot find module '@serverless-stack/core' from 'src/util/permission.ts'". I haven't made any changes yet. I can see @serverless-stack/core is a dependency in package.json but I'm naively assuming that lerna should have handled that? I've never used yarn before nor lerna.

$ yarn yarn install v1.22.11 [1/4] Resolving packages... success Already up-to-date. $ lerna run prepare --scope='{@serverless-stack/resources,@serverless-stack/cli,create-serverless-stack}' lerna notice cli v3.22.1 lerna notice filter including "{@serverless-stack/resources,@serverless-stack/cli,create-serverless-stack}" lerna info filter [ lerna info filter '{@serverless-stack/resources,@serverless-stack/cli,create-serverless-stack}' lerna info filter ] lerna info Executing command in 3 packages: "yarn run prepare" lerna info run Ran npm script 'prepare' in 'create-serverless-stack' in 0.4s: yarn run v1.22.11 $ node ./bin/get-cdk-version.js Syncing with aws-cdk version 1.111.0 Done in 0.13s. lerna info run Ran npm script 'prepare' in '@serverless-stack/resources' in 6.3s: yarn run v1.22.11 $ node ./bin/aws-cdk-version-check.js && npm run build ✅ AWS CDK versions in @serverless-stack/resources is in sync with @serverless-stack/core

@serverless-stack/resources@0.37.2 build

tsc --rootDir src --outDir dist && cd assets/stub && yarn && cd ../.. && node ./bin/create-stub-zip.js

[1/4] Resolving packages... success Already up-to-date. ✅ Stub Lambda is successfully created. Done in 6.08s. lerna info run Ran npm script 'prepare' in '@serverless-stack/cli' in 0.3s: yarn run v1.22.11 $ node ./bin/sync-cdk-version.js ✅ AWS CDK packages in @serverless-stack/cli are in sync with @serverless-stack/core Done in 0.18s. lerna success run Ran npm script 'prepare' in 3 packages in 6.7s: lerna success - @serverless-stack/cli lerna success - create-serverless-stack lerna success - @serverless-stack/resources Done in 8.47s.

and yarn test test/StaticSite.test.ts yarn run v1.22.11 $ jest test/StaticSite.test.ts FAIL test/StaticSite.test.ts ● Test suite failed to run Cannot find module '@serverless-stack/core' from 'src/util/permission.ts' Require stack: src/util/permission.ts src/Function.ts src/Api.ts src/index.ts test/StaticSite.test.ts 3 | import * as cdk from "@aws-cdk/core"; 4 | import * as iam from "@aws-cdk/aws-iam"; > 5 | import { getChildLogger } from "@serverless-stack/core"; | ^ 6 | import { 7 | Api, 8 | Table, at Resolver.resolveModule (../../node_modules/jest-resolve/build/index.js30611) at Object.<anonymous> (src/util/permission.ts51) Test Suites: 1 failed, 1 total Tests: 0 total Snapshots: 0 total Time: 1.579 s Ran all test suites matching /test\/StaticSite.test.ts/i. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

it worked for me.. let me pull in @Jay and see if he can spot anything

@Jay Warwick is working on a PR, and is having some trouble running the resources test

From the error, it seems importing

@serverless-stack/core

is failing within

@serverless-stack/resources

Those should all be symlinks

I'm on node16 btw

In core

I think we need to add core to

postinstall

of the root package.json

@Warwick Grigg I'm merging a PR that should fix your issue. Additionally we made it so you can run

yarn watch

in the root and it'll run a watcher across the projects in the monorepo that use TS

@Frank I've submitted a new PR which includes updated documentation.