@doikayt/typescript-build-config 0.1.30 → 0.1.32

package/README.md

@@ -143,7 +143,7 @@ The screen cast below shows the process for Level 1. Note:
   not doikayt) we see:
   - no repos initially
   - no doikayt aliases registered in `.bashrc`
-- After we run `dk-scaffold demo`, we will see:
+- After we run `dk-scaffold demo`, we need to input 'y' to install, then we see:
   - lots of output showing the project being configured and built
   - a push to GitHub
   - a build and release triggered on GitHub
@@ -158,6 +158,15 @@ The screen cast below shows the process for Level 1. Note:
     alt="update-markdown-toc demo">
 </p>
 
+After we ran the screen cast steps we were able to screenshot how our push triggered a build o
+onthe  Github CI servers.
+
+<p align="center">
+  <img
+    src="docs/github-actions.png"
+    width="720"
+    alt="github-actions-view">
+</p>
 
 
 
@@ -165,7 +174,8 @@ The screen cast below shows the process for Level 1. Note:
 
 The  package housed in this repo is designed to be 'upstream-most' -- i.e., all other
 packages depend on it (possibly transitively) and this package has no other 
-dependencies in this repo.
+dependencies on `doikait` packages (except ONE pinned version specific dependency on build_tools
+which we rely on for documentation generation. -- Cycles are generally bad, but this one works!)
 
 Two goals drive every design decision made for this package, and they pull in different
 directions:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@doikayt/typescript-build-config",
-  "version": "0.1.30",
+  "version": "0.1.32",
   "description": "Shared build configuration for TypeScript projects — ESLint, Prettier, tsconfig, and Playwright presets",
   "_comments": {
     "exports": "This block lists the config files that will be extended by files in in src/toplevel - which are copied to consuming project root folder. An example: eslint.config.js imports from '@doikayt/typescript-build-config/eslint'.",