@movable/ui 4.0.1 → 4.0.2-alpha.0

package/package.json

@@ -1,16 +1,12 @@
 {
   "name": "@movable/ui",
-  "version": "4.0.1",
+  "version": "4.0.2-alpha.0",
   "description": "Movable Ink's shared MUI components and MUI theme for our vite applications",
   "module": "lib/index.mjs",
   "types": "lib/index.d.ts",
   "files": [
     "lib"
   ],
-  "workspaces": [
-    "eslint-plugin-ui",
-    "mcp-server"
-  ],
   "scripts": {
     "build": "vite build",
     "build-storybook": "storybook build",
@@ -19,7 +15,6 @@
     "lint:src": "tsc --project ./tsconfig.json && eslint -c ./.eslintrc.json ./src --report-unused-disable-directives --max-warnings 0",
     "lint:cypress": "tsc --project ./cypress/tsconfig.json && eslint -c ./cypress/.eslintrc.json ./cypress --resolve-plugins-relative-to ./cypress --report-unused-disable-directives --max-warnings 0 --no-error-on-unmatched-pattern",
     "lint:stories": "tsc --project ./tsconfig.json && eslint -c ./.eslintrc.json ./stories --report-unused-disable-directives --max-warnings 0",
-    "prepare": "husky install",
     "percy:storybook": "PERCY_TOKEN=$PERCY_TOKEN percy exec -- percy storybook ./storybook-static",
     "storybook": "storybook dev -p 6006",
     "test": "cypress run --component -q",
@@ -29,7 +24,8 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/movableink/ui.git"
+    "url": "git+https://github.com/movableink/ui.git",
+    "directory": "packages/ui"
   },
   "keywords": [
     "mui",
@@ -43,12 +39,9 @@
   },
   "homepage": "https://movableink.github.io/ui",
   "devDependencies": {
-    "@commitlint/cli": "^17.6.7",
-    "@commitlint/config-conventional": "^17.6.7",
     "@emotion/react": "^11.11.1",
     "@emotion/styled": "^11.11.0",
     "@movable/eslint-plugin-ui": "*",
-    "@movable/prettier-config": "^2.0.0",
     "@mui/icons-material": "^6.5.0",
     "@mui/material": "^6.5.0",
     "@mui/x-data-grid-generator": "^7.29.8",
@@ -79,13 +72,10 @@
     "eslint-plugin-react-hooks": "^4.6.0",
     "eslint-plugin-react-refresh": "^0.4.3",
     "eslint-plugin-storybook": "^9.1.4",
-    "husky": "^8.0.0",
-    "lint-staged": "^13.2.3",
     "lodash-es": "^4.17.21",
     "notistack": "^3.0.1",
     "npm-run-all": "^4.1.5",
     "postcss": "^8.4.27",
-    "prettier": "3.1.1",
     "react": "^18.2.0",
     "react-chartjs-2": "^5.3.0",
     "react-dom": "^18.2.0",
@@ -115,8 +105,5 @@
   },
   "optionalDependencies": {
     "@rollup/rollup-linux-x64-gnu": "4.9.5"
-  },
-  "volta": {
-    "node": "22.21.1"
   }
 }

package/README.md

@@ -1,136 +0,0 @@
-# @movable/ui
-
-todo: update
-
-This repo contains the shared components for our frontend applications. Using this [react component library guide](https://prateeksurana.me/blog/react-component-library-using-storybook-7/#compiling-the-library-using-rollup)
-
-## Local Development
-
-### Installation
-
-1. Ensure you have [`volta`](https://volta.sh) installed on your computer
-2. Clone the repo
-3. `npm install` (note: `npm`, not `yarn`)
-
-### Usage
-
-Ensure the project consuming this library has all the required peer dependencies.
-
-### WARNING: Providing Theme Colors to Custom Components
-
-While within using app you'll be able to use `(theme) => theme.palette...` style of sx props. But within our custom component this _does NOT_ traverse to the using app. You'll want to use the theme palette directly to ensure proper color strings. See #224
-
-```jsx
-import palette from 'path_to_src/theme/palette';
-
-export default InkCustomComponent() {
-  return (
-    <Box sx={{ backgroundColor: palette.neutral50 }}>
-      ...
-    </Box>
-  )
-}
-```
-
-## Alpha Pre-release Workflow
-
-This project supports alpha releases for testing changes before full releases.
-
-### Manual Alpha Release
-For testing specific features or changes:
-
-1. **Navigate to Actions tab** in GitHub repository
-2. **Select "Release to NPM"** workflow
-3. **Click "Run workflow"** button
-4. **Configure options:**
-   - `release_type`: Select `prerelease`
-   - `dist_tag`: Leave as `alpha` or customize (e.g., `beta`, `feature-test`)
-   - `increment`: Leave empty for auto-increment or specify (`patch`, `minor`, `major`)
-5. **Click "Run workflow"** to trigger the release
-
-**Result:** Creates version like `3.4.1-alpha.0` and publishes to npm with `@alpha` tag
-
-### Using Alpha Versions in Other Projects
-
-Install alpha versions in your consuming projects:
-
-```bash
-# Install latest alpha
-npm install @movable/ui@alpha
-yarn add @movable/ui@alpha
-
-# Install specific alpha version
-npm install @movable/ui@3.4.1-alpha.0
-yarn add @movable/ui@3.4.1-alpha.0
-```
-
-View all available versions at: https://www.npmjs.com/package/@movable/ui?activeTab=versions
-
-## Claude Code Skills
-
-This repo includes local [Claude Code](https://claude.com/claude-code) skills for common workflows. See [CLAUDE.md](./CLAUDE.md#local-skills) for the full list of available `/slash` commands.
-
-## MCP Server
-
-This repo includes an MCP (Model Context Protocol) server that exposes component information to AI assistants like Claude Code. See [mcp-server/README.md](./mcp-server/README.md) for setup instructions.
-
-## Visual Regression Testing
-
-Visual regression testing is handled via **Percy with Storybook** (Storybook-only approach):
-
-- **Storybook Stories**: All visual states must be captured in Storybook stories
-- **Percy Integration**: `npm run percy:storybook` runs Percy snapshots on built Storybook
-- **Cypress Tests**: Focus on functional/integration testing only (no Percy snapshots)
-
-This consolidated approach reduces duplicate snapshots and CI runtime while maintaining comprehensive visual coverage.
-
-## Conventional Commits
-
-This repo uses [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) to drive automated versioning. Commits are linted both pre-commit and in PR checks.
-
-**Breaking changes** must use `feat!:` or include a `BREAKING CHANGE:` footer — see [CONTRIBUTING.md](./CONTRIBUTING.md#breaking-changes) for details.
-
-```
-fix(percy): added percy snapshots for all component states
-
-- active
-- disabled
-- focused
-```
-
-## GitHub Issue to Shortcut Sync
-
-This repository automatically syncs GitHub issues to Shortcut stories on the Designer Team board. **GitHub Issues are the source of truth** - all work should start and be managed here.
-
-### For Engineers
-
-📖 **See [.github/SHORTCUT_SYNC.md](.github/SHORTCUT_SYNC.md) for the complete workflow guide**, including:
-- How the automation works (automatic + manual triggers)
-- Recommended workflow for working through issues
-- Issue types and state transitions
-- Troubleshooting common scenarios
-
-**Quick summary:** When you open an issue, it automatically creates a Shortcut story. When you open a PR that fixes the issue, it moves the story to "In Development". When you close the issue, it completes the story.
-
-### Updating the Shortcut API Token
-
-If the Shortcut API token needs to be rotated or updated:
-
-1. **Create a new token in Shortcut:**
-   - Go to [Shortcut Settings → API Tokens](https://app.shortcut.com/settings/account/api-tokens)
-   - Create new token with description "GitHub Issue Sync"
-   - Copy the token value
-
-2. **Update the GitHub secret:**
-
-   Via GitHub CLI:
-   ```bash
-   gh secret set SHORTCUT_API_TOKEN
-   # Paste the new token when prompted
-   ```
-
-   Or via GitHub web UI:
-   - Go to Settings → Secrets and variables → Actions
-   - Click on `SHORTCUT_API_TOKEN` and update the value
-
-3. **Test the automation** by creating a test issue to verify the sync is working