Publish the React and Vue open-source core and documentation

[elreco]

CodeRocket UI becomes the active project in this existing repository, preserving its stars, issues and history. The MIT core includes 48 components and 26 blocks for both React and Vue, shared design tokens/specifications, CLI and read-only MCP integration. Documentation source is public under docs/content; the hosted Studio, accounts, database and AI services remain private.

Vue Tailwind Datepicker is preserved under legacy/vue-tailwind-datepicker, with its original license, npm API and documentation. Historical release workflows are archived and inactive. The legacy branch and final tag retain the original directory layout. No npm package is unpublished or automatically released.

Both frameworks build independently, including Vue SFC compilation, declarations and complete stylesheets. A source manifest and a companion private deployment check keep the published core and documentation aligned with the hosted application. The README and transition guides now explain both frameworks. Legacy canonical URLs, sitemap and sharing metadata preserve the historical documentation.

Validation: frozen-lockfile installation; React/TypeScript and Vue typechecks; eight package builds; 179 unit tests; standalone React/Vue SSR, export paths, CSS and consumer types. Legacy documentation builds pass for the root domain and GitHub Pages base. Hosted application: 393 tests, typechecks and production build pass.

[netlify]

✅ Deploy Preview for vue-tailwind-datepicker ready!

Name	Link
🔨 Latest commit	d224908
🔍 Latest deploy log	https://app.netlify.com/projects/vue-tailwind-datepicker/deploys/6aafde0a98aae3000861aa0b
😎 Deploy Preview	https://deploy-preview-180--vue-tailwind-datepicker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
37471814	Triggered	Generic High Entropy Secret	19d5ff7	.coderocket/source-manifest.json	View secret
37471815	Triggered	Generic High Entropy Secret	19d5ff7	.coderocket/source-manifest.json	View secret
37471816	Triggered	Generic Password	19d5ff7	.coderocket/source-manifest.json	View secret
37471817	Triggered	Generic High Entropy Secret	19d5ff7	.coderocket/source-manifest.json	View secret
37471818	Triggered	Generic High Entropy Secret	19d5ff7	.coderocket/source-manifest.json	View secret
37471819	Triggered	Generic High Entropy Secret	19d5ff7	.coderocket/source-manifest.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}