import-project

You can import a project archive by providing the archive path to a .tar.gz bundle. The tool extracts components and pages, placing them into the correct src directories and updating project indexes automatically.

When importing components and pages, you can specify a conflict strategy to rename, replace, or skip conflicting files. This ensures the import aligns with your existing project structure without overwriting critical files unintentionally.

Yes, importing a project bundle automatically updates documentation. The tool refreshes docs/components.md and docs/pages.md to reflect the newly imported files and their references.

Yes, you can rehydrate a shared project bundle for a new environment. The tool parses the bundle manifest and applies your chosen conflict strategy to quickly establish the project structure without manual reconfiguration.

Yes, Bash tooling is required for archive extraction, manifest parsing, and file copy operations. The import process relies on these local tools to place files correctly and update project indexes.

Manual archive imports risk hand-editing errors because components and pages must be placed into specific src directories. Automating the manifest parsing and index updates eliminates the risk of misaligned files and broken references.