@limetech/limepkg-cpq-order 2.10.4 → 2.10.5-dev.3

package/frontend/dist/types/index.cjs.js

@@ -0,0 +1,2 @@
+'use strict';
+

package/frontend/dist/types/index.js

@@ -0,0 +1 @@
+

package/package.json

@@ -1,10 +1,12 @@
 {
     "name": "@limetech/limepkg-cpq-order",
-    "version": "2.10.4",
+    "version": "2.10.5-dev.3",
     "description": "Type definitions for limepkg-cpq-order frontend",
-    "main": "index.d.ts",
+    "module": "frontend/dist/types/index.js",
+    "main": "frontend/dist/types/index.cjs.js",
+    "types": "frontend/dist/types/index.d.ts",
     "files": [
-        "**/*.d.ts"
+        "frontend/dist/types/"
     ],
     "keywords": [
         "limepkg",
@@ -18,6 +20,9 @@
         "access": "public"
     },
     "scripts": {
-        "prepublishOnly": "cp -R ../dist/types/* ./"
+        "prepare": "npx rollup -c"
+    },
+    "devDependencies": {
+        "rollup": "^4.30.1"
     }
 }

package/readme.md

@@ -0,0 +1,7 @@
+# Lime CPQ
+
+## NPM package
+
+Whenever Lime CPQ is built, an NPM package is also built and published to `@limetech/limepkg-cpq-order` with a matching version number.
+
+If we do any **breaking changes to the interfaces**, the major version of Lime CPQ **must be bumped**! Otherwise there's a risk that consuming solutions won't build anymore due to their `frontend` not passing the linting.