Hey guys, Is there any examples for setting up sst with yarn workspaces in typescript?

Shouldn't be anything special

@thdxr When I add a my package into the package json in services, it was showing not found error.

Can I see the error?

@thdxr Here is the error

When going between packages you cannot import typescript files

I tried building it. But I could see that that @packages/common in node_modules still has typescript code

it should also have js code

Yeah that would be awesome 😄

Here is my core package - similar to your common package.

OMG. It worked. 😮

sweet 👍🏽

@thdxr Do you build the core package separately ? or does it build when running

sst start

or

sst deploy

?

I usually have a watcher on it, it is kind of annoying

Aha. I see. Thanks.

I’m having a similiar problem using the new example you made @thdxr https://github.com/serverless-stack/serverless-stack/tree/master/examples/typescript When execute an api I receive this error:

Waiting for the debugger to disconnect...
7b27afef-1906-48c9-81a8-c92c15644c03 ERROR Error: Cannot find module '@linkey/types'
Require stack:
- /Users/GioMaligno/Workspace/linkey/backend/.build/services/stations/index.js

From your example I added a workspace for types (to share type between backend and frontend) as described in the root package.json

"workspaces": ["backend", "types"]

Types tsconfig:

{
  "extends": "../tsconfig.json",
  "include": ["index.ts"],
  "compilerOptions": {
    "declaration": true,
    "outDir": "dist",
    "experimentalDecorators": true,
    "baseUrl": ".",
    "paths": {
      "@linkey/types": ["index.ts"],
    },
    "strictPropertyInitialization": false
  }
}

Types package.json:

{
  "name": "@linkey/types",
  "version": "0.1.4",
  "scripts": {
    "build": "sst build",
    "script": "esr",
    "test": "jest"
  },
  "dependencies": {
    "class-validator": "^0.13.1"
  },
  "devDependencies": {
    "esbuild-runner": "^2.2.1",
    "jest": "^27.2.0"
  }
}

Backend tsconfig:

{
  "extends": "../tsconfig.json",
  "include": ["core", "services", "test", "scripts"],
  "compilerOptions": {
    "declaration": true,
    "outDir": "dist",
    "experimentalDecorators": true,
    "baseUrl": ".",
    "paths": {
      "@linkey/core": ["core"],
    },
    "strictPropertyInitialization": false
  }
}

Backend package.json :

{
  "name": "@linkey/backend",
  "version": "0.0.1",
  "scripts": {
    "build": "sst build",
    "script": "esr",
    "test": "jest"
  },
  "dependencies": {
    "@linkey/types": "0.1.4",
    "@types/aws-lambda": "^8.10.83",
    "class-transformer": "^0.4.0"
  },
  "devDependencies": {
    "@types/aws4": "^1.5.2",
    "@types/supertest": "^2.0.11",
    "aws4": "^1.11.0",
    "esbuild-runner": "^2.2.1",
    "jest": "^27.2.0",
    "supertest": "^6.1.6"
  }
}

In my node_module folder @linkey/backend was built on “.build” folder instead of @linkey/types which is never build (no .build folder). It is the first time I use Yarn Workspace I suppose to make some huge mistake 🤔

I don't think I would make types its own package

I thought to model a types module to keep synchronized models on both side. Did you see drawbacks on this approach?

That is a good approach but remember creating a new

package.json

means extra complexity

Yes I could include type folder in backend workspace. For every app I could import types from backend workspace.

or in its own folder