injast-core 1.0.79 → 1.0.80

package/README.md

@@ -124,7 +124,15 @@ import "injast-core/fonts.css";
 
 ## Figma Make
 
-Figma Make users should select the public npm package named `injast-core`. Do not use `@alimohammadiwork/injast-core`; that is a different scoped package name.
+Figma Make users should select the public npm package named `injast-core`. Do not use `@alimohammadiwork/injast-core` or `@make-kits/injast-core-make-kit` for the public package path.
+
+If the package selector ranks unrelated `core` packages when searching `injast-core`, search for:
+
+```text
+injast
+```
+
+Then select `injast-core` from the public unscoped package results.
 
 For Make kits, start with the included guidelines:
 

package/guidelines/Guidelines.md

@@ -33,7 +33,9 @@ Read focused component files before using those component groups:
 ## Package Rules
 
 - Install and import the public package as `injast-core`.
+- In Figma Make package search, use `injast` if exact `injast-core` search ranks unrelated `core` packages first.
 - Do not import `@alimohammadiwork/injast-core`; that scoped package is not this package.
+- Do not use `@make-kits/injast-core-make-kit` for the public npm package path.
 - For Figma Make and Vite React apps, use `SPAThemeProvider`.
 - Import `injast-core/fonts.css` once near the app root.
 - Use named imports from `injast-core` for common usage; use subpath imports for focused entrypoints.

package/guidelines/setup.md

@@ -11,10 +11,10 @@ npm install injast-core
 For Figma Make package selection, search for:
 
 ```text
-injast-core
+injast
 ```
 
-Do not search for or install `@alimohammadiwork/injast-core`.
+Then select the public unscoped package `injast-core`. If exact search for `injast-core` returns unrelated `core` packages first, use `injast` as the search term. Do not search for or install `@alimohammadiwork/injast-core` or `@make-kits/injast-core-make-kit` for this public package path.
 
 ## Required Imports
 
@@ -84,6 +84,6 @@ import { formatPersianNumber } from "injast-core/utils";
 ## Build Assumptions
 
 - The package is ESM and Vite-compatible.
-- React 18 and React 19 are supported by peer dependency range.
+- React 18 is the default target for Figma Make. React 19 is also allowed by the package peer dependency range for non-Figma consumers.
 - CSS imports from dependencies must be allowed because `MobileDatePicker` imports `react-multi-date-picker` CSS.
 - Do not add custom Tailwind setup for Injast Core. Styling comes from Material UI theme, component `sx` props, and package CSS.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "injast-core",
-  "version": "1.0.79",
+  "version": "1.0.80",
   "description": "Reusable Injast React and Material UI components, providers, hooks, utilities, and design tokens.",
   "type": "module",
   "main": "dist/index.js",
@@ -94,8 +94,14 @@
     "access": "public"
   },
   "keywords": [
+    "injast-core",
     "injast",
     "react",
+    "react-18",
+    "vite",
+    "figma-make",
+    "make-kit",
+    "design-system-package",
     "material-ui",
     "mui",
     "components",
@@ -140,13 +146,13 @@
     "@types/jalaali-js": "^1.1.3",
     "@types/lodash": "^4.17.14",
     "@types/node": "^22.10.7",
-    "@types/react": "^19",
-    "@types/react-dom": "^19",
+    "@types/react": "^18.3.12",
+    "@types/react-dom": "^18.3.1",
     "@types/stylis": "^4.2.7",
     "eslint": "^9",
     "eslint-plugin-storybook": "^10.2.3",
-    "react": "^19.0.0",
-    "react-dom": "^19.0.0",
+    "react": "^18.2.0",
+    "react-dom": "^18.2.0",
     "storybook": "^10.2.3",
     "typescript": "^5.7.3",
     "vite": "^6.0.0",