@choonkeat/md-serve 0.6.3 → 0.8.0

package/README.md

@@ -43,7 +43,7 @@ rendering isn't what you want:
 | Append to a URL | What you get |
 | --- | --- |
 | `?listing=1` | The bare file listing for a directory — even when an `index.html` or `README.md` would otherwise take over. This is what the **Home** breadcrumb links to. |
-| `?pretty=0` | The **raw source** of a file that normally renders — e.g. `README.md?pretty=0` or `index.html?pretty=0` returns the bytes as `text/plain` instead of the rendered page. |
+| `?pretty=0` | The **raw source** of a file that normally renders — e.g. `README.md?pretty=0` or `index.html?pretty=0` returns the bytes as `text/plain` instead of the rendered page. On a *directory* URL it's a synonym for `?listing=1`: same rule, "give me the plain thing", applied to a directory. |
 | `?pretty=1` | A **syntax-highlighted** view of a source file, with linkable line numbers (e.g. `main.go?pretty=1#L42`). |
 
 ## Install
@@ -84,8 +84,10 @@ md-serve -version
   `Home / <file>` breadcrumb — the **Home** crumb (a link to
   `?listing=1`) drops you to the bare file listing. Otherwise a plain
   generated listing with **Name / Size / Modified** columns. Appending
-  `?listing=1` to any directory URL forces that listing, bypassing
-  `index.html` too.
+  `?listing=1` (or `?pretty=0`) to any directory URL forces that listing,
+  bypassing `index.html` too. Click any column header to sort by it (click again to
+  reverse); the choice is remembered across pages. Folders stay grouped
+  above files, and `Modified` is shown in your browser's own timezone.
 - Everything else is served byte-for-byte. That means `.js`, `.css`,
   `.wasm`, `.json`, images, fonts, and the rest all reach the browser
   with their normal MIME types — ES module scripts load, fetch() works,
@@ -123,7 +125,8 @@ md-serve -version
 ## Develop
 
 ```sh
-make build              # cross-compile all 6 platform binaries → npm-platforms/
+make build              # cross-compile all 6 platform binaries → npm-platforms/, then link
+make link               # just the link step: put this checkout's md-serve on PATH
 make test               # go vet
 make publish-dry        # rehearse the npm publish
 make publish            # ship to npm
@@ -135,6 +138,14 @@ right `@choonkeat/md-serve-<platform>-<arch>` optionalDependency at
 runtime, falling back to a locally built binary in `npm-platforms/`
 during development.
 
+That fallback is what makes `make build` enough to run your own changes:
+`npm link` symlinks the shim onto your PATH, and the shim prefers
+`npm-platforms/` over the published package, so `md-serve` means "this
+working tree". `make build` prints the resolved path and version banner
+so you can see which build you're about to run. One thing it can't
+reach: `npx @choonkeat/md-serve` resolves from the npx cache and keeps
+running the last *published* release regardless.
+
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@choonkeat/md-serve",
-  "version": "0.6.3",
+  "version": "0.8.0",
   "description": "Tiny static file server that renders Markdown as GitHub-styled HTML",
   "type": "module",
   "bin": {
@@ -19,11 +19,11 @@
   },
   "license": "MIT",
   "optionalDependencies": {
-    "@choonkeat/md-serve-darwin-arm64": "0.6.3",
-    "@choonkeat/md-serve-darwin-x64": "0.6.3",
-    "@choonkeat/md-serve-linux-arm64": "0.6.3",
-    "@choonkeat/md-serve-linux-x64": "0.6.3",
-    "@choonkeat/md-serve-win32-arm64": "0.6.3",
-    "@choonkeat/md-serve-win32-x64": "0.6.3"
+    "@choonkeat/md-serve-darwin-arm64": "0.8.0",
+    "@choonkeat/md-serve-darwin-x64": "0.8.0",
+    "@choonkeat/md-serve-linux-arm64": "0.8.0",
+    "@choonkeat/md-serve-linux-x64": "0.8.0",
+    "@choonkeat/md-serve-win32-arm64": "0.8.0",
+    "@choonkeat/md-serve-win32-x64": "0.8.0"
   }
 }