@o-a/cms-agent 0.1.5 → 0.1.6

package/README.md

@@ -58,7 +58,7 @@ Either way, the result is the same:
 ```
 cd my-site/vhost
 npm install
-node server.js
+npm start
 ```
 
 Visit `http://localhost:3000`. `create-site` prints a real API token to

package/dist/create-site/cli.js

@@ -17,10 +17,10 @@ try {
     console.log('Next steps:');
     console.log(`  cd ${targetArg}/vhost`);
     console.log('  npm install');
-    console.log('  node server.js');
+    console.log('  npm start');
     console.log('');
     console.log('Want to edit this site from a hosted admin while developing locally?');
-    console.log('  node server.js --tunnel');
+    console.log('  npm run tunnel');
 }
 catch (error) {
     if (error instanceof ScaffoldError) {

package/dist/create-site/generate-site.js

@@ -94,6 +94,16 @@ export function scaffoldSite(targetDir) {
         version: '0.0.0',
         private: true,
         type: 'module',
+        // "start" matters beyond convenience: several PaaS platforms
+        // auto-detect and run `npm start` by default for a Node app
+        // with no other deploy config - without this, a site pushed
+        // straight to one of those (no Dockerfile in the loop) simply
+        // wouldn't boot. "tunnel" mirrors the --tunnel flag create-site
+        // already tells the operator about in its own next-steps output.
+        scripts: {
+            start: 'node server.js',
+            tunnel: 'node server.js --tunnel',
+        },
         dependencies: {
             // Pinned exact, never a ^range - at v0.x even a minor bump
             // can be breaking (build plan's own word is "pinned").

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@o-a/cms-agent",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "type": "module",
   "publishConfig": {
     "access": "public"