kempo 4.2.34 → 4.2.36

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +2 -0
  2. package/package.json +2 -1
package/README.md CHANGED
@@ -416,6 +416,8 @@ npm test
416
416
 
417
417
  `.env.example` has the matching `DATABASE_URL`. The suite seeds its own groups and permissions, and cleans up the rows it creates.
418
418
 
419
+ `npm test` (`kempo-test -n`) only runs the Node-side suite. Admin components that need a real DOM run in an actual browser via `npm run test:browser` — no database or running server required, since it exercises the real component/SDK code with only `window.fetch` intercepted for canned responses. It temporarily junctions `/kempo-ui`, `/kempo-css` and `/kempo` onto `node_modules`/`dist` at the project root so the admin bundle's absolute imports resolve against kempo-testing-framework's static test server, and removes them afterward regardless of pass/fail.
420
+
419
421
  ### Building for Distribution
420
422
 
421
423
  When preparing the framework for npm release, minify and optimize the source code:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "kempo",
3
- "version": "4.2.34",
3
+ "version": "4.2.36",
4
4
  "type": "module",
5
5
  "description": "A fullstack CMS framework for creating websites with user authentication",
6
6
  "scripts": {
@@ -14,6 +14,7 @@
14
14
  "test:email": "node ./scripts/test-email.js",
15
15
  "test": "kempo-test -n",
16
16
  "test:node": "kempo-test -n",
17
+ "test:browser": "node scripts/run-browser-tests.js",
17
18
  "link:local": "npm install ../kempo-server ../kempo-ui --no-save",
18
19
  "db:reset": "node ./scripts/reset-db.js"
19
20
  },