![]() packages/monorepo-packageĪnd we do update. The Docusaurus website consumes its own monorepo packages, exposed as symlinks I don't understand what you mean here, this is the default mode of a Yarn workspace and all monorepos I work on behave this way. Why you need this? It is fully unsafe, it will not work with yarn PnP, pnpm, etc? There is a bug related to the dev server not recompiling when a node_modules/monorepo-linked-package is updating, requiring to run yarn start again to see the changes (or find another way to trigger the recompilation, which is very slow because the dev cache had to be disabled).Disabling the cache works but is not manageable, particularly slowing down the dev experience. There is a bug related to the cache, that I can confirm, affecting both dev/prod builds, and may be solved by PR fix: fix FileSystemInfo#createSnapshot with symbol link #12254.We use MDX and our mdx-loader should be able to handle all the content of that symlinked directly (but nothing more, because we use multiple mdx loaders). We want to turn symlinks: false because we are a doc tool and our users want to use symlinks for the root folder of their docs (containing markdown file), as this folder can come from another directly. Netlify prod/deploy previews deploy stale code due to persistent caching.Ĭhange PR, than can serve as a repro: facebook/docusaurus#5126 + yarn install & yarn start:v2 + yarn watch. ![]() dev only hot reload for changes in some parts the codebase (packages using Yarn workspace symlinks).Also affected by this with Docusaurus, since turning symlinks from true to false I see a lot of problems in our monorepo:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |