To pass the built files from src-pkg to dist-pkg, i only need to point the folder in tsc ( tsc -project. Package.json → build + test + publish script The tree structure would move from: myLib/ So I thought: why not elevate it all to be a monorepo? Turning point I'd still have to build a test app to test my library on the DX level, and where to host it?.the cp package.json dist/ part would grow to have *.md, and who knows what else/how it'd grow (and I'd like not to have build script files).Then I thought that to test this, I'd be npm link my dist/ folder, virtually creating 'a package in package' with few problems:

The easiest fix is to cp package.json dist/ & npm publish dist/, and here you go, problem solved. You can fix this by using package.json's main field, but that'd do only for the top-level module you could use exports, but it doesn't work well with Typescript. 48 How to use yarn workspaces with typescript and out folders Load 7 more related questions Show. 2 Angular and yarn workspace : missing file at TS compilation time. Nothing incredibly exotic there, but if you've been doing that, you know that publishing this will result in your import paths to contain dist later on. Use yarn workspaces and typescripts project references to reference another package subdirectory. I started my first attempt with a simple single package, tsconfig and src/, tests/ and dist/ folder. I found about this thread and cross-referenced for exposure. I want to propose multiple modules and make the import easy to use, similar to (for example) nextjs's next/Router. The DX (Developer Experience) is the most important thing for us, and for such I'm picking the latest trends in dev: Typescript, esm, etc. I'm creating a package for my company, which going to be released publicly. I added a simple import in the client/src/App.I'm looking for feedback on a pattern I coded while tinkering around. 'utils': '1.0.0', // also tried 'utils': 'workspace:packages/utils' Uses esbuild + nodemon to reload the server in development mode (even when workspace dependencies are changed). Uses a shareable ESLint config and Jest config to provide an extensible linting and testing setup. 'name': 'monorepo with shared library and yarn 2 workspaces',Ĭonsole.log('this is a function from the shared library ') Uses Yarn workspaces to make it easy to work within the monorepo.

Previously I was just publishing the TypeScript files alongside their JavaScript code in the same directory. I am trying to properly build the project packages using TypeScript. Configuring workspace monorepo to use prettier and eslint with typescript. The base TypeScript configuration for projects in the. When trying to run the client app I receive the error:Ĭannot find module 'utils' or its corresponding type declarations. This uses yarn workspaces, TypeScript, Jest, ts-jest and ESLint with eslint-plugin-import. If you use the yarn client, this file will be yarn.lock instead. Unfortunately, I have not been able to make it work since few days (and a lot of googling.). The root-level project contains a package.json file, as does each workspace. I use yarn 2 workspaces and wanted to avoid using larna (if possible). In Yarn parlance, these modules are called workspaces. I want to set up a project with a client part (react-app), a server part (express) and a shared library (utils) in typescript.

Yarn workspaces typescript