Type errors occur at vercel dev
runtime, probably because vercel cli is ignoring the typescript version of the project.
Overriding the version does not solve this problem.
- Install dependencies.
npm i
- Create new vercel project and link to this repository.
vercel
-
Change the root directory to
src
at the project settings page. -
Import the project settings to local.
vercel pull
- Start server.
npm start
-
Access to API endpoints.
-
Your terminal will report type errors like below.
Satisfies Operator
api/satisfies-operator.ts:9:3 - error TS1005: ',' expected.
} satisfies Record<Colors, string | RGB>;
api/satisfies-operator.ts:9:13 - error TS1005: ',' expected.
} satisfies Record<Colors, string | RGB>;
api/satisfies-operator.ts:9:19 - error TS1005: ',' expected.
} satisfies Record<Colors, string | RGB>;
api/satisfies-operator.ts:9:26 - error TS1005: '>' expected.
} satisfies Record<Colors, string | RGB>;
api/satisfies-operator.ts:9:41 - error TS1109: Expression expected.
} satisfies Record<Colors, string | RGB>;
Found 5 errors.
Private Identifiers
api/private-identifiers.ts:4:3 - error TS18028: Private identifiers are only available when targeting ECMAScript 2015 and higher.
#_message() {
Found 1 error.