library-build-sync

Build JavaScript/TypeScript packages and synchronize them into the React template.

70|3|Updated Jun 23, 2020

Search Tags:#template #library #build #monorepo #sync #yarn #turborepo

Ready to run

npx skills add https://github.com/InfinityLoopLabs/Blank_Platform --skill library-build-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: library-build-sync
Source: https://github.com/InfinityLoopLabs/Blank_Platform/tree/main/skills/library-build-sync
Command: npx skills add https://github.com/InfinityLoopLabs/Blank_Platform --skill library-build-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents the React template from using stale local library code by ensuring changed JavaScript/TypeScript packages are built and the template reinstall is performed so the latest local library versions are picked up.

Core Features & Use Cases

Ensures deterministic propagation of local package builds into the React template used by repository scaffolding.
Supports single-package and multi-package workflows; run individual package builds or a full repo library build before updating the template.
Includes clear guardrails (build first, then run yarn in the template) to avoid inconsistent template dependency states.
Use Case: After modifying a shared UI component package, build that package and then refresh the React template so newly generated projects include the updated component.

Quick Start

Build the changed package with yarn build and then run yarn inside _templates/react_template so the template consumes the updated local library.

Frequently Asked Questions about library-build-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sync local library builds into a React template in a monorepo?▼

Sync local builds by running yarn build for changed packages, then running yarn inside the _templates/react_template directory to ensure the template consumes the latest local library versions.

Why does my React template use stale local library code after modifying packages in a Turborepo monorepo?▼

The React template uses stale local library code because changed packages must be rebuilt and the template reinstalled to ensure generated projects pick up the latest local package versions.

What is the best way to ensure deterministic propagation of local package builds into a React template?▼

Build changed JavaScript or TypeScript packages first, then run yarn inside _templates/react_template to refresh dependencies and ensure deterministic propagation of local package builds.

Do I need to run yarn build before updating the React template with local package changes?▼

Yes, you need to run yarn build for affected packages to generate updated artifacts, then run yarn inside _templates/react_template so the React template consumes the latest local package versions.

Can I use this workflow to sync multiple modified packages into the React template at once?▼

Yes, you can run a full repo library build for multiple packages, then run yarn inside _templates/react_template to synchronize all updated local packages into the React template at once.

What are the limitations of manually copying local builds into a React template without reinstalling dependencies?▼

Manually copying local builds without reinstalling dependencies leads to inconsistent template dependency states, which is why you must run yarn inside _templates/react_template after building packages.