create-node-lib 2.15.3 → 2.15.4

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.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,10 @@
1
+ ## [2.15.4](https://github.com/lirantal/create-node-lib/compare/v2.15.3...v2.15.4) (2026-04-13)
2
+
3
+
4
+ ### Bug Fixes
5
+
6
+ * support term info from host ([3509575](https://github.com/lirantal/create-node-lib/commit/35095752e422b9e3352b661fd1217c69354737ab))
7
+
1
8
  ## [2.15.3](https://github.com/lirantal/create-node-lib/compare/v2.15.2...v2.15.3) (2026-04-12)
2
9
 
3
10
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-node-lib",
3
- "version": "2.15.3",
3
+ "version": "2.15.4",
4
4
  "description": "Scaffolding out a Node.js library module",
5
5
  "bin": "./bin/cli.js",
6
6
  "engines": {
@@ -77,4 +77,10 @@ fi
77
77
  npx --yes "@devcontainers/cli@${CLI_VERSION}" up "${UP_ARGS[@]}"
78
78
 
79
79
  echo "Dropping into container shell..."
80
- npx --yes "@devcontainers/cli@${CLI_VERSION}" exec --workspace-folder "$WORKSPACE_FOLDER" bash
80
+ # Resolve TERM to something the container's terminfo knows about.
81
+ # Terminals like kitty, ghostty, alacritty set custom TERM values the container won't have.
82
+ # Fall back to xterm-256color (truecolor still works via COLORTERM=truecolor).
83
+ if ! infocmp "${TERM:-xterm-256color}" &>/dev/null 2>&1; then
84
+ TERM=xterm-256color
85
+ fi
86
+ TERM="${TERM:-xterm-256color}" npx --yes @devcontainers/cli@${CLI_VERSION} exec --workspace-folder "$WORKSPACE_FOLDER" -- env TERM="${TERM:-xterm-256color}" COLORTERM=truecolor bash