@doikayt/typescript-build-config 0.1.30 → 0.1.31

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 +10 -1
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -143,7 +143,7 @@ The screen cast below shows the process for Level 1. Note:
143
143
  not doikayt) we see:
144
144
  - no repos initially
145
145
  - no doikayt aliases registered in `.bashrc`
146
- - After we run `dk-scaffold demo`, we will see:
146
+ - After we run `dk-scaffold demo`, we need to input 'y' to install, then we see:
147
147
  - lots of output showing the project being configured and built
148
148
  - a push to GitHub
149
149
  - a build and release triggered on GitHub
@@ -158,6 +158,15 @@ The screen cast below shows the process for Level 1. Note:
158
158
  alt="update-markdown-toc demo">
159
159
  </p>
160
160
 
161
+ After we ran the screen cast steps we were able to screenshot how our push triggered a build o
162
+ onthe Github CI servers.
163
+
164
+ <p align="center">
165
+ <img
166
+ src="docs/github-actions.png"
167
+ width="720"
168
+ alt="github-actions-view">
169
+ </p>
161
170
 
162
171
 
163
172
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@doikayt/typescript-build-config",
3
- "version": "0.1.30",
3
+ "version": "0.1.31",
4
4
  "description": "Shared build configuration for TypeScript projects — ESLint, Prettier, tsconfig, and Playwright presets",
5
5
  "_comments": {
6
6
  "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'.",