fix(cdk): fixed missing ts-node when running in pipeline

Author: Bender

Diff for: README.md

@@ -42,6 +42,7 @@ This library uses Cloudfront, S3, ApiGateway and Lambdas to deploy easily in sec
 - [x] [GetServerSideProps](https://nextjs.org/docs/basic-features/data-fetching/get-server-side-props)
 - [x] [GetStaticProps](https://nextjs.org/docs/basic-features/data-fetching/get-static-props)
 - [x] NextJS rewrites (next.config.js)
+- [x] Monorepo support
 - [ ] [ISR and fallbacks](https://nextjs.org/docs/basic-features/data-fetching/incremental-static-regeneration)
 - [ ] [Streaming](https://nextjs.org/docs/advanced-features/react-18/streaming)
 - [ ] Custom babel configuration

Diff for: lib/cli/deploy.ts

@@ -9,10 +9,8 @@ interface Props {
 const cdkExecutable = require.resolve('aws-cdk/bin/cdk')
 
 export const deployHandler = async ({ stackName, tsconfigPath, appPath }: Props) => {
-	// Not using SWC as it's problematic on NPX (postinstall fails).
-	// NPX so ts-node does not need to be a dependency.
 	// All paths are absolute.
-	const cdkApp = `npx ts-node --project ${tsconfigPath} ${appPath}`
+	const cdkApp = `node -r ts-node/register --project ${tsconfigPath} ${appPath}`
 	const cdkCiFlags = `--require-approval never --ci`
 
 	await executeAsyncCmd({