v1.11.4

.vscode/settings.json

@@ -1,7 +1,7 @@
 {
   "json.schemas": [
     {
-      "fileMatch": ["/npmextra.json"],
+      "fileMatch": ["/.smartconfig.json"],
       "schema": {
         "type": "object",
         "properties": {

changelog.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 2026-03-24 - 1.11.4 - fix(config)
+rename npmextra configuration to .smartconfig.json and align publish packaging with updated config handling
+
+- replaces packaged config file references from npmextra.json to .smartconfig.json
+- updates publish module typings and null checks for tsPublishJson, package info, and file paths
+- bumps build and runtime dependencies to newer compatible versions
+- simplifies tsconfig.json by removing unused baseUrl and paths settings
+- refreshes README content to document current CLI, registry, and package publishing behavior
+
 ## 2026-03-24 - 1.11.3 - fix(config)
 replace npmextra with smartconfig for base registry resolution
 

license

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Task Venture Capital GmbH
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@git.zone/tspublish",
-  "version": "1.11.3",
+  "version": "1.11.4",
   "private": false,
   "description": "A tool to publish multiple, concise, and small packages from monorepos, specifically for TypeScript projects within a git environment.",
   "main": "dist_ts/index.js",
@@ -17,11 +17,11 @@
     "tspublish": "./cli.js"
   },
   "devDependencies": {
-    "@git.zone/tsbuild": "^4.0.2",
+    "@git.zone/tsbuild": "^4.4.0",
-    "@git.zone/tsbundle": "^2.6.3",
+    "@git.zone/tsbundle": "^2.10.0",
     "@git.zone/tsrun": "^2.0.1",
-    "@git.zone/tstest": "^3.1.3",
+    "@git.zone/tstest": "^3.5.1",
-    "@types/node": "^25.0.2"
+    "@types/node": "^25.5.0"
   },
   "repository": {
     "type": "git",
@@ -43,21 +43,21 @@
     "dist_ts_web/**/*",
     "assets/**/*",
     "cli.js",
-    "npmextra.json",
+    ".smartconfig.json",
     "readme.md"
   ],
   "dependencies": {
     "@push.rocks/consolecolor": "^2.0.3",
-    "@push.rocks/smartconfig": "^6.0.0",
+    "@push.rocks/smartcli": "^4.0.20",
-    "@push.rocks/smartcli": "^4.0.19",
+    "@push.rocks/smartconfig": "^6.0.1",
     "@push.rocks/smartdelay": "^3.0.5",
     "@push.rocks/smartfile": "^13.1.2",
-    "@push.rocks/smartfs": "^1.3.1",
+    "@push.rocks/smartfs": "^1.5.0",
-    "@push.rocks/smartlog": "^3.1.10",
+    "@push.rocks/smartlog": "^3.2.1",
     "@push.rocks/smartnpm": "^2.0.6",
     "@push.rocks/smartpath": "^6.0.0",
     "@push.rocks/smartrequest": "^5.0.1",
-    "@push.rocks/smartshell": "^3.3.7"
+    "@push.rocks/smartshell": "^3.3.8"
   },
   "keywords": [
     "typescript",

readme.md

@@ -7,7 +7,7 @@
 
 ## 🌟 What is tspublish?
 
-`@git.zone/tspublish` is your Swiss Army knife for managing and publishing multiple TypeScript packages from a monorepo. It automates the tedious parts of package publishing while giving you full control over the process. Whether you're maintaining a suite of microservices, a component library, or any collection of related packages, tspublish makes your life easier.
+`@git.zone/tspublish` is a powerful CLI tool and library for managing and publishing multiple TypeScript packages from a monorepo. It automates the tedious parts of package publishing — discovery, dependency resolution, building, version validation, and multi-registry publishing — while giving you full control over the process. Whether you're maintaining a suite of microservices, a component library, or any collection of related packages, tspublish makes your life dramatically easier.
 
 ## Issue Reporting and Security
 
@@ -15,62 +15,54 @@ For reporting bugs, issues, or security vulnerabilities, please visit [community
 
 ### ✨ Key Features
 
-- 📦 **Automatic Package Discovery** - Scans your monorepo for publishable packages
+- 📦 **Automatic Package Discovery** — Scans your monorepo for publishable `ts*` directories
-- 🎨 **Beautiful CLI Output** - Color-coded logging with progress indicators
+- 🎨 **Beautiful CLI Output** — Color-coded logging with progress bars and status indicators
-- 🔍 **Version Collision Detection** - Prevents accidental overwrites
+- 🔍 **Version Collision Detection** — Prevents accidental overwrites by checking the registry first
-- 🏗️ **Build Integration** - Automatically builds TypeScript before publishing
+- 🏗️ **Build Integration** — Automatically compiles TypeScript before publishing via `@git.zone/tsbuild`
-- 🎯 **Smart Dependency Management** - Inherits dependencies from your monorepo
+- 🎯 **Smart Dependency Management** — Inherits dependency versions from your monorepo's `package.json`
-- 🌐 **Multi-Registry Support** - Publish to npm, GitHub packages, or private registries
+- 🌐 **Multi-Registry Support** — Publish to npm, GitHub Packages, Gitea, or private registries
-- ⚡ **Zero Config** - Works out of the box with sensible defaults
+- 🔗 **Base Registry Inheritance** — Use `useBase` / `extendBase` to inherit registries from `.smartconfig.json`
+- ⚡ **CLI Binary Support** — Automatically generates `cli.js` wrappers for publishable CLI packages
+- 🧹 **Clean Builds** — Creates isolated `dist_publish_*` directories for each package
 
 ## 📥 Installation
 
-### As a Development Dependency (Recommended)
-
 ```bash
 # Using pnpm (recommended)
 pnpm add -D @git.zone/tspublish
 
-# Using npm
+# Global installation for CLI usage
-npm install --save-dev @git.zone/tspublish
+pnpm add -g @git.zone/tspublish
-
-# Using yarn
-yarn add -D @git.zone/tspublish
-```
-
-### Global Installation
-
-```bash
-npm install -g @git.zone/tspublish
 ```
 
 ## 🚀 Quick Start
 
 ### 1️⃣ Structure Your Monorepo
 
-Organize your packages with the `ts` prefix convention:
+Organize your packages using directories that start with `ts`:
 
 ```
 my-awesome-monorepo/
-├── package.json          # Main monorepo package.json
+├── package.json            # Main monorepo package.json (version is inherited)
-├── tsconfig.json         # Shared TypeScript config
+├── tsconfig.json           # Shared TypeScript config
-├── ts-core/              # Core package
+├── .smartconfig.json       # Optional: base registry configuration
-│   ├── ts/               # TypeScript source files
+├── ts_core/                # Core package
-│   ├── readme.md         # Package documentation
+│   ├── index.ts            # Entry point
-│   └── tspublish.json    # Publishing configuration
+│   ├── readme.md           # Package-specific documentation
-├── ts-utils/             # Utilities package
+│   └── tspublish.json      # Publishing configuration
-│   ├── ts/
+├── ts_utils/               # Utilities package
+│   ├── index.ts
 │   ├── readme.md
 │   └── tspublish.json
-└── ts-cli/               # CLI package
+└── ts_cli/                 # CLI package
-    ├── ts/
+    ├── index.ts
     ├── readme.md
     └── tspublish.json
 ```
 
 ### 2️⃣ Configure Each Package
 
-Create a `tspublish.json` in each package directory:
+Create a `tspublish.json` in each publishable directory:
 
 ```json
 {
@@ -81,10 +73,9 @@ Create a `tspublish.json` in each package directory:
     "@push.rocks/smartfile"
   ],
   "registries": [
-    "registry.npmjs.org:public",
+    "registry.npmjs.org:public"
-    "npm.pkg.github.com:private"
   ],
-  "bin": ["my-cli"]
+  "bin": []
 }
 ```
 
@@ -92,22 +83,118 @@ Create a `tspublish.json` in each package directory:
 
 | Field | Type | Description |
 |-------|------|-------------|
-| `name` | string | Package name (required) |
+| `name` | `string` | The published package name (e.g., `@myorg/core`) |
-| `order` | number | Build order for interdependent packages |
+| `order` | `number` | Build order for interdependent packages (lower builds first) |
-| `dependencies` | string[] | Dependencies from the monorepo to include |
+| `dependencies` | `string[]` | Dependencies to include — versions are resolved from the monorepo's `package.json` |
-| `registries` | string[] | Target registries with access level |
+| `registries` | `string[]` | Target registries with access level (format: `"url:accessLevel"`) |
-| `bin` | string[] | CLI executable names |
+| `bin` | `string[]` | CLI executable names (generates a `cli.js` wrapper automatically) |
 
-### 3️⃣ Run the Publisher
+### 3️⃣ Publish
-
-#### Command Line
 
 ```bash
 # From your monorepo root
 npx tspublish
 ```
 
-#### Programmatic Usage
+That's it! tspublish will discover all `ts*` directories containing `tspublish.json`, build them in order, validate versions against the registry, and publish.
+
+## 🎯 Advanced Usage
+
+### Registry Configuration
+
+TSPublish offers three approaches for configuring target registries:
+
+#### 1. Explicit Registries
+
+Define specific registries directly in `tspublish.json`:
+
+```json
+{
+  "registries": [
+    "registry.npmjs.org:public",
+    "npm.pkg.github.com:private"
+  ]
+}
+```
+
+The format is `"registryUrl:accessLevel"` where `accessLevel` is `public` or `private`.
+
+#### 2. Use Base Configuration (`useBase`)
+
+Inherit registries from your project's `.smartconfig.json` (managed by `@git.zone/cli`):
+
+```json
+{
+  "registries": ["useBase"]
+}
+```
+
+This reads from `.smartconfig.json` at the key `@git.zone/cli.release.registries`.
+
+#### 3. Extend Base Configuration (`extendBase`)
+
+Start with base registries and add or remove specific ones:
+
+```json
+{
+  "registries": [
+    "extendBase",
+    "custom-registry.example.com:public",
+    "-https://registry.npmjs.org"
+  ]
+}
+```
+
+The `-` prefix excludes a registry from the base configuration. All other entries (besides `extendBase`) are added.
+
+#### Empty Registries
+
+If `registries` is an empty array `[]`, the package will be built but **not published** — useful for internal-only packages that other packages depend on.
+
+### Build Order Management
+
+When packages depend on each other, use the `order` field to control build sequence:
+
+```json
+// ts_core/tspublish.json — builds first
+{
+  "name": "@myorg/core",
+  "order": 1,
+  "dependencies": [],
+  "registries": ["useBase"],
+  "bin": []
+}
+
+// ts_utils/tspublish.json — builds second, depends on core
+{
+  "name": "@myorg/utils",
+  "order": 2,
+  "dependencies": ["@myorg/core"],
+  "registries": ["useBase"],
+  "bin": []
+}
+```
+
+### CLI Binary Packages
+
+For packages that ship CLI tools, specify the binary names in the `bin` array:
+
+```json
+{
+  "name": "@myorg/cli",
+  "order": 3,
+  "dependencies": ["commander", "@myorg/core"],
+  "registries": ["registry.npmjs.org:public"],
+  "bin": ["my-cli", "my-tool"]
+}
+```
+
+TSPublish will:
+1. Fetch the standard `cli.js` template from the `@git.zone/cli` assets repository
+2. Adjust the import path to point to the correct `dist_*` folder
+3. Configure the `bin` field in the generated `package.json`
+
+### Programmatic Usage
 
 ```typescript
 import { TsPublish } from '@git.zone/tspublish';
@@ -116,283 +203,133 @@ const publisher = new TsPublish();
 await publisher.publish(process.cwd());
 ```
 
-## 🎯 Advanced Usage
+#### Custom Publishing Pipeline
-
-### Custom Publishing Pipeline
 
 ```typescript
 import { TsPublish, PublishModule } from '@git.zone/tspublish';
 
-// Initialize the publisher
 const publisher = new TsPublish();
-
-// Get all publishable modules
 const modules = await publisher.getModuleSubDirs('./my-monorepo');
 
-// Custom processing for each module
 for (const [name, config] of Object.entries(modules)) {
-  const module = new PublishModule(publisher, {
+  const mod = new PublishModule(publisher, {
     monoRepoDir: './my-monorepo',
-    packageSubFolder: name
+    packageSubFolder: name,
   });
 
-  // Initialize module
+  await mod.init();                   // Resolve deps, validate version
-  await module.init();
+  await mod.createPublishModuleDir(); // Scaffold dist_publish_* directory
-  
+  await mod.build();                  // Compile TypeScript
-  // Create publish directory
+  await mod.publish();                // Publish to registries
-  await module.createPublishModuleDir();
-  
-  // Custom build step
-  console.log(`Building ${config.name}...`);
-  await module.build();
-  
-  // Publish to registries
-  await module.publish();
 }
 ```
 
-### Registry Configuration
-
-TSPublish supports multiple registries with different access levels. You have three approaches:
-
-#### 1️⃣ Explicit Registries
-
-Define specific registries directly in your `tspublish.json`:
-
-```json
-{
-  "registries": [
-    "registry.npmjs.org:public",        // Public npm package
-    "npm.pkg.github.com:private",       // Private GitHub package
-    "my-company.jfrog.io/npm:restricted" // Corporate registry
-  ]
-}
-```
-
-#### 2️⃣ Use Base Configuration (`useBase`)
-
-Inherit registries from your project's `npmextra.json` configuration (managed by `gitzone config`):
-
-```json
-{
-  "registries": ["useBase"]
-}
-```
-
-This reads from `npmextra.json` under `@git.zone/cli.release.registries`.
-
-#### 3️⃣ Extend Base Configuration (`extendBase`)
-
-Start with base registries and add/remove specific ones:
-
-```json
-{
-  "registries": [
-    "extendBase",
-    "custom-registry.example.com:public",
-    "-https://registry.npmjs.org"  // Exclude this registry
-  ]
-}
-```
-
-The `-` prefix excludes a registry from the base configuration.
-
-#### Empty Registries
-
-If no registries are configured, the package will be built but **not published** (a warning is logged).
-
-### Build Order Management
-
-When packages depend on each other, use the `order` field to ensure correct build sequence:
-
-```json
-// ts-core/tspublish.json
-{
-  "name": "@myorg/core",
-  "order": 1,
-  "dependencies": []
-}
-
-// ts-utils/tspublish.json
-{
-  "name": "@myorg/utils",
-  "order": 2,
-  "dependencies": ["@myorg/core"]
-}
-```
-
-### CLI Binary Configuration
-
-For packages that include CLI tools:
-
-```json
-{
-  "name": "@myorg/cli",
-  "bin": ["my-cli", "my-tool"],
-  "dependencies": ["commander", "chalk"]
-}
-```
-
-This automatically generates the necessary `cli.js` wrapper and configures the package.json `bin` field.
-
-## 🎨 Beautiful Output
-
-TSPublish provides rich, colored console output with:
-
-- 📊 Progress bars for multi-package operations
-- 🎯 Clear status indicators (ℹ info, ✓ success, ⚠ warning, ✖ error)
-- 📦 Package-specific icons and formatting
-- 🚀 Visual separators between operation phases
-
 ## 🔧 How It Works
 
-1. **Discovery Phase** 🔍
+```
-   - Scans for directories starting with `ts`
+┌──────────────────────────────────────────────────────────┐
-   - Validates `tspublish.json` presence
+│                   tspublish pipeline                     │
-   - Orders packages by dependency
+├──────────────────────────────────────────────────────────┤
-
+│                                                          │
-2. **Preparation Phase** 📋
+│  1. 🔍 Discovery                                        │
-   - Creates temporary `dist_publish_*` directories
+│     Scan for ts* directories containing tspublish.json   │
-   - Generates package.json from tspublish.json
+│                                                          │
-   - Copies source files and assets
+│  2. 📋 Preparation                                      │
-   - Sets up TypeScript configuration
+│     Create dist_publish_* with generated package.json,   │
-
+│     tsconfig.json, source files, readme, and license     │
-3. **Build Phase** 🔨
+│                                                          │
-   - Runs TypeScript compilation
+│  3. 🔨 Build                                            │
-   - Generates declaration files
+│     Run `tsbuild tsfolders` in the publish directory     │
-   - Prepares distribution bundle
+│                                                          │
-
+│  4. ✅ Validation                                       │
-4. **Validation Phase** ✅
+│     Check npm registry — abort if version already exists │
-   - Checks npm registry for existing versions
+│                                                          │
-   - Prevents accidental overwrites
+│  5. 🚀 Publish                                          │
-   - Validates package metadata
+│     pnpm publish to each configured registry             │
-
+│                                                          │
-5. **Publishing Phase** 🚀
+└──────────────────────────────────────────────────────────┘
-   - Publishes to configured registries
-   - Handles authentication
-   - Reports success/failure
-
-## 🤝 Integration with CI/CD
-
-### GitHub Actions
-
-```yaml
-name: Publish Packages
-
-on:
-  push:
-    tags:
-      - 'v*'
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      
-      - uses: pnpm/action-setup@v2
-        with:
-          version: 8
-          
-      - uses: actions/setup-node@v3
-        with:
-          node-version: '20'
-          cache: 'pnpm'
-          
-      - run: pnpm install
-      
-      - run: pnpm build
-      
-      - run: npx tspublish
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 ```
 
-### GitLab CI
+For each discovered module, tspublish:
 
-```yaml
+1. **Discovers** all directories starting with `ts` that contain a `tspublish.json`
-publish:
+2. **Resolves dependencies** from the monorepo's `package.json`, using the monorepo version for packages not found in `dependencies`
-  stage: deploy
+3. **Creates an isolated publish directory** (`dist_publish_<folder>`) with a generated `package.json`, `tsconfig.json`, source code copy, readme, and license
-  image: node:20
+4. **Builds** the package using `pnpm run build` (which calls `tsbuild tsfolders`)
-  before_script:
+5. **Validates** against the target registry — if the name+version already exists, it exits with an error
-    - npm install -g pnpm
+6. **Publishes** to each configured registry via `pnpm publish`
-    - pnpm install
-  script:
-    - pnpm build
-    - npx tspublish
-  only:
-    - tags
-```
 
 ## 📚 API Reference
 
-### TsPublish Class
+### TsPublish
 
 ```typescript
 class TsPublish {
-  // Publish all packages in a monorepo
+  /** Publish all discovered modules in a monorepo directory */
-  async publish(monorepoDirPath: string): Promise<void>
+  async publish(monorepoDirPath: string): Promise<void>;
 
-  // Get all publishable module configurations
+  /** Discover and return all publishable modules with their tspublish.json configs */
-  async getModuleSubDirs(dirPath: string): Promise<{[key: string]: ITsPublishJson}>
+  async getModuleSubDirs(dirPath: string): Promise<Record<string, ITsPublishJson>>;
 }
 ```
 
-### PublishModule Class
+### PublishModule
 
 ```typescript
 class PublishModule {
-  // Initialize the module for publishing
+  /** Initialize: resolve dependencies, validate version against registry */
-  async init(): Promise<void>
+  async init(): Promise<void>;
 
-  // Create the publishing directory structure
+  /** Create the dist_publish_* directory with all necessary files */
-  async createPublishModuleDir(): Promise<void>
+  async createPublishModuleDir(): Promise<void>;
 
-  // Build the TypeScript package
+  /** Build the TypeScript package */
-  async build(): Promise<void>
+  async build(): Promise<void>;
 
-  // Publish to configured registries
+  /** Publish to all configured registries */
-  async publish(): Promise<void>
+  async publish(): Promise<void>;
 }
 ```
 
-### ITsPublishJson Interface
+### ITsPublishJson
 
 ```typescript
 interface ITsPublishJson {
-  name: string           // Package name
+  name: string;           // Published package name
-  order: number          // Build order
+  order: number;          // Build sequence (lower = earlier)
-  dependencies: string[] // Dependencies to include
+  dependencies: string[]; // Dependencies to include from monorepo
-  registries: string[]   // Target registries
+  registries: string[];   // Target registries ("url:accessLevel", "useBase", or "extendBase")
-  bin: string[]         // CLI binaries
+  bin: string[];          // CLI binary names
+}
+```
+
+### GiteaAssets
+
+```typescript
+class GiteaAssets {
+  constructor(options: { giteaBaseUrl: string; token?: string });
+
+  /** Fetch files from a Gitea repository directory */
+  async getFiles(owner: string, repo: string, directory: string, branch?: string): Promise<IRepoFile[]>;
+
+  /** Get the standard cli.js entry file template */
+  async getBinCliEntryFile(): Promise<IRepoFile>;
 }
 ```
 
 ## 🐛 Troubleshooting
 
-### Common Issues
+| Problem | Solution |
-
+|---------|----------|
-**Package already exists with version X.X.X**
+| **"Package X already exists with version Y"** | Bump the version in your monorepo's `package.json` |
-- TSPublish detected a version collision
+| **No publish modules found** | Ensure directories start with `ts` and contain a valid `tspublish.json` |
-- Update your monorepo's package.json version
+| **Build failures** | Check TypeScript errors — tspublish runs `tsbuild tsfolders` in the generated directory |
-- Or unpublish the existing version if appropriate
+| **useBase/extendBase error** | Ensure `.smartconfig.json` has registries at `@git.zone/cli.release.registries` |
-
+| **Missing dependency versions** | Add the dependency to your monorepo's `package.json` `dependencies` field |
-**No publish modules found**
-- Ensure your packages follow the `ts-*` naming convention
-- Check that each package has a valid `tspublish.json`
-
-**Build failures**
-- Verify TypeScript configuration
-- Check that all dependencies are installed
-- Review the build output for specific errors
-
-**useBase/extendBase error**
-- Ensure your `npmextra.json` has registries configured at `@git.zone/cli.release.registries`
-- Use `gitzone config add <registry-url>` to configure base registries
 
 ## License and Legal Information
 
-This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the [LICENSE](./LICENSE) file.
+This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the [license](./license) file.
 
 **Please note:** The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.
 

ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@git.zone/tspublish',
-  version: '1.11.3',
+  version: '1.11.4',
   description: 'A tool to publish multiple, concise, and small packages from monorepos, specifically for TypeScript projects within a git environment.'
 }

ts/classes.publishmodule.ts

@@ -52,7 +52,7 @@ export class PublishModule {
       ...this.options.dependencies,
       ...(() => {
         const resultDependencies = {};
-        for (const dependency of this.options.tsPublishJson.dependencies) {
+        for (const dependency of this.options.tsPublishJson!.dependencies) {
           if (monoRepoPackageJson.dependencies[dependency]) {
             resultDependencies[dependency] = monoRepoPackageJson.dependencies[dependency];
           } else {
@@ -62,14 +62,14 @@ export class PublishModule {
         return resultDependencies;
       })(),
     };
-    this.options.name = this.options.name || this.options.tsPublishJson.name;
+    this.options.name = this.options.name || this.options.tsPublishJson!.name;
     this.options.version = monoRepoPackageJson.version;
 
     // now that we have a name and version, lets check if there is already a package under the same name and version.
     const smartnpmInstance = new plugins.smartnpm.NpmRegistry({}); // TODO: pass in options
-    let packageInfo: plugins.smartnpm.NpmPackage;
+    let packageInfo: plugins.smartnpm.NpmPackage | undefined;
     try {
-      packageInfo = await smartnpmInstance.getPackageInfo(this.options.name);
+      packageInfo = await smartnpmInstance.getPackageInfo(this.options.name!);
     } catch (error) {
       logWarn(`Package ${this.options.name} does not yet seem to exist. Proceeding in 10 seconds...`);
       await plugins.smartdelay.delayFor(10000);
@@ -77,7 +77,7 @@ export class PublishModule {
     if (packageInfo) {
       const availableVersions = packageInfo.allVersions.map((versionArg) => versionArg.version);
       logInfo(`Available versions for ${this.options.name}: ${availableVersions.join(', ')}`);
-      if (availableVersions.includes(this.options.version)) {
+      if (availableVersions.includes(this.options.version!)) {
         logError(
           `Package ${this.options.name} already exists with version ${this.options.version}`
         );
@@ -152,13 +152,13 @@ export class PublishModule {
         'dist_ts_web/**/*',
         'assets/**/*',
         'cli.js',
-        'smartconfig.json',
+        '.smartconfig.json',
         'readme.md',
       ],
-      ...this.options.tsPublishJson.bin ? {
+      ...this.options.tsPublishJson?.bin ? {
         bin: (() => {
           const binObject: {[key: string]: string} = {};
-          for (const bin of this.options.tsPublishJson.bin) {
+          for (const bin of this.options.tsPublishJson!.bin) {
             binObject[bin] = `./cli.js`;
           }
           return binObject;
@@ -192,10 +192,10 @@ export class PublishModule {
 
     // ts subfolder, the folder that contains the source code and is being transpiled
     const destSubFolder = plugins.path.join(this.options.publishModDirFullPath, this.options.packageSubFolder);
-    await plugins.smartfs.directory(this.options.packageSubFolderFullPath).recursive().copy(destSubFolder);
+    await plugins.smartfs.directory(this.options.packageSubFolderFullPath!).recursive().copy(destSubFolder);
 
     // readme
-    const readmeSrc = plugins.path.join(this.options.packageSubFolderFullPath, 'readme.md');
+    const readmeSrc = plugins.path.join(this.options.packageSubFolderFullPath!, 'readme.md');
     const readmeDest = plugins.path.join(this.options.publishModDirFullPath, 'readme.md');
     await plugins.smartfs.file(readmeSrc).copy(readmeDest);
 
@@ -219,17 +219,17 @@ export class PublishModule {
 
   public async createBinCliSetup() {
     const binSetupApplies: boolean =
-      this.options.tsPublishJson.bin &&
+      !!this.options.tsPublishJson?.bin &&
-      Array.isArray(this.options.tsPublishJson.bin) &&
+      Array.isArray(this.options.tsPublishJson!.bin) &&
-      this.options.tsPublishJson.bin.length > 0;
+      this.options.tsPublishJson!.bin.length > 0;
     const files = await this.tsPublishRef.giteaAssetsInstance.getFiles(
       'git.zone',
       'cli',
       'assets/templates/cli/cli.js'
     );
     const indexPath = `./dist_${this.options.packageSubFolder}/index.js`;
-    const fileContent = atob(files[0].base64Content).replace('./dist_ts/index.js', indexPath);
+    const fileContent = atob(files[0].base64Content!).replace('./dist_ts/index.js', indexPath);
-    const cliJsPath = plugins.path.join(this.options.publishModDirFullPath, 'cli.js');
+    const cliJsPath = plugins.path.join(this.options.publishModDirFullPath!, 'cli.js');
     await plugins.smartfs.file(cliJsPath).encoding('utf8').write(fileContent);
   }
 

tsconfig.json

@@ -6,9 +6,7 @@
     "module": "NodeNext",
     "moduleResolution": "NodeNext",
     "esModuleInterop": true,
-    "verbatimModuleSyntax": true,
+    "verbatimModuleSyntax": true
-    "baseUrl": ".",
-    "paths": {}
   },
   "exclude": [
     "dist_*/**/*.d.ts"