meocord 4.0.0-beta.2 → 4.0.0-beta.3

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # meocord
 
+## 4.0.0-beta.3
+
+### Patch Changes
+
+- [#40](https://github.com/l7aromeo/meocord/pull/40) [`3629edd`](https://github.com/l7aromeo/meocord/commit/3629eddaf20bd0947d24e5582aa167b2c0ca0d47) Thanks [@l7aromeo](https://github.com/l7aromeo)! - Lint `meocord.config.ts`. The shared ESLint config from `meocord/eslint` ignored it, so the config
+  alone skipped the rules every other file follows — unused imports, formatting. It is linted like the
+  rest now; the typecheck it already gets is unchanged.
+
+- [#40](https://github.com/l7aromeo/meocord/pull/40) [`80b8302`](https://github.com/l7aromeo/meocord/commit/80b83021894ef8a964a12ac1610c2ec9b40f344e) Thanks [@l7aromeo](https://github.com/l7aromeo)! - Exit with code 1 when the login fails, whatever the entry point does. `app.start()` now sets
+  `process.exitCode = 1` before rejecting, so an existing `main.ts` whose `catch` only logs the error no
+  longer exits 0 — no `process.exitCode = 1` needs adding to it, and new applications' `main.ts` no
+  longer carries one.
+
 ## 4.0.0-beta.2
 
 ### Major Changes

package/dist/cjs/core/index.cjs

@@ -109,9 +109,12 @@ class MeoCordApp {
     /**
    * Registers the Discord event handlers and logs in.
    *
-   * Rejects when the login fails -- an invalid token, or Discord unreachable -- so the caller can
-   * stop with a non-zero exit code. A bot that never came online is a failed start, and a
-   * supervisor such as Docker's `restart: on-failure` or systemd can only tell if the process says so.
+   * Rejects when the login fails -- an invalid token, or Discord unreachable -- and sets the exit
+   * code to 1 first. A bot that never came online is a failed start, and a supervisor such as
+   * Docker's `restart: on-failure` or systemd can only tell if the process says so. The exit code is
+   * set here rather than left to the entry point because an entry point that catches the rejection
+   * to log it has handled it, and the process would otherwise end with 0. A later `start()` that
+   * logs in -- an entry point retrying -- clears the code again, if this is what set it.
    */ async start() {
         this.logger.log('Starting bot...');
         this.bot.on('clientReady', ()=>this.runListener('clientReady', async ()=>{
@@ -128,7 +131,19 @@ class MeoCordApp {
                     user,
                     action: enum_index.ReactionHandlerAction.REMOVE
                 })));
-        await this.bot.login(this.discordToken);
+        try {
+            await this.bot.login(this.discordToken);
+        } catch (error) {
+            if (process.exitCode === undefined || process.exitCode === 0) {
+                process.exitCode = 1;
+                MeoCordApp.failedLoginSetExitCode = true;
+            }
+            throw error;
+        }
+        if (MeoCordApp.failedLoginSetExitCode && process.exitCode === 1) {
+            process.exitCode = undefined;
+            MeoCordApp.failedLoginSetExitCode = false;
+        }
         this.logger.log('Bot is online!');
     }
     async registerCommands() {
@@ -508,6 +523,7 @@ class MeoCordApp {
         process.on('SIGTERM', ()=>this.gracefulShutdown());
     }
 }
+/** Whether a failed login set the process exit code, so a later successful one knows to clear it. */ MeoCordApp.failedLoginSetExitCode = false;
 
 /**
  * File written beside a bundle that carries native addons, naming the platform it was built for.

package/dist/esm/bin/app-template/src/main.ts.template

@@ -11,8 +11,4 @@ async function bootstrap() {
   logger.log('Application started')
 }
 
-bootstrap().catch(error => {
-  logger.error('Error during startup:', error)
-  // A bot that never came online is a failed start: exit non-zero, so Docker, systemd or CI see it.
-  process.exitCode = 1
-})
+bootstrap().catch(error => logger.error('Error during startup:', error))

package/dist/esm/core/meocord.app.js

@@ -91,9 +91,12 @@ class MeoCordApp {
     /**
    * Registers the Discord event handlers and logs in.
    *
-   * Rejects when the login fails -- an invalid token, or Discord unreachable -- so the caller can
-   * stop with a non-zero exit code. A bot that never came online is a failed start, and a
-   * supervisor such as Docker's `restart: on-failure` or systemd can only tell if the process says so.
+   * Rejects when the login fails -- an invalid token, or Discord unreachable -- and sets the exit
+   * code to 1 first. A bot that never came online is a failed start, and a supervisor such as
+   * Docker's `restart: on-failure` or systemd can only tell if the process says so. The exit code is
+   * set here rather than left to the entry point because an entry point that catches the rejection
+   * to log it has handled it, and the process would otherwise end with 0. A later `start()` that
+   * logs in -- an entry point retrying -- clears the code again, if this is what set it.
    */ async start() {
         this.logger.log('Starting bot...');
         this.bot.on('clientReady', ()=>this.runListener('clientReady', async ()=>{
@@ -110,7 +113,19 @@ class MeoCordApp {
                     user,
                     action: ReactionHandlerAction.REMOVE
                 })));
-        await this.bot.login(this.discordToken);
+        try {
+            await this.bot.login(this.discordToken);
+        } catch (error) {
+            if (process.exitCode === undefined || process.exitCode === 0) {
+                process.exitCode = 1;
+                MeoCordApp.failedLoginSetExitCode = true;
+            }
+            throw error;
+        }
+        if (MeoCordApp.failedLoginSetExitCode && process.exitCode === 1) {
+            process.exitCode = undefined;
+            MeoCordApp.failedLoginSetExitCode = false;
+        }
         this.logger.log('Bot is online!');
     }
     async registerCommands() {
@@ -490,5 +505,6 @@ class MeoCordApp {
         process.on('SIGTERM', ()=>this.gracefulShutdown());
     }
 }
+/** Whether a failed login set the process exit code, so a later successful one knows to clear it. */ MeoCordApp.failedLoginSetExitCode = false;
 
 export { MeoCordApp };

package/dist/esm/package.json.js

@@ -1,4 +1,4 @@
-var version = "4.0.0-beta.2";
+var version = "4.0.0-beta.3";
 var packageJson = {
 	version: version};
 

package/dist/types/core/index.d.cts

@@ -39,12 +39,17 @@ declare class MeoCordApp {
      */
     private updateActivity;
     private getInstance;
+    /** Whether a failed login set the process exit code, so a later successful one knows to clear it. */
+    private static failedLoginSetExitCode;
     /**
      * Registers the Discord event handlers and logs in.
      *
-     * Rejects when the login fails -- an invalid token, or Discord unreachable -- so the caller can
-     * stop with a non-zero exit code. A bot that never came online is a failed start, and a
-     * supervisor such as Docker's `restart: on-failure` or systemd can only tell if the process says so.
+     * Rejects when the login fails -- an invalid token, or Discord unreachable -- and sets the exit
+     * code to 1 first. A bot that never came online is a failed start, and a supervisor such as
+     * Docker's `restart: on-failure` or systemd can only tell if the process says so. The exit code is
+     * set here rather than left to the entry point because an entry point that catches the rejection
+     * to log it has handled it, and the process would otherwise end with 0. A later `start()` that
+     * logs in -- an entry point retrying -- clears the code again, if this is what set it.
      */
     start(): Promise<void>;
     registerCommands(): Promise<void>;

package/dist/types/core/index.d.ts

@@ -39,12 +39,17 @@ declare class MeoCordApp {
      */
     private updateActivity;
     private getInstance;
+    /** Whether a failed login set the process exit code, so a later successful one knows to clear it. */
+    private static failedLoginSetExitCode;
     /**
      * Registers the Discord event handlers and logs in.
      *
-     * Rejects when the login fails -- an invalid token, or Discord unreachable -- so the caller can
-     * stop with a non-zero exit code. A bot that never came online is a failed start, and a
-     * supervisor such as Docker's `restart: on-failure` or systemd can only tell if the process says so.
+     * Rejects when the login fails -- an invalid token, or Discord unreachable -- and sets the exit
+     * code to 1 first. A bot that never came online is a failed start, and a supervisor such as
+     * Docker's `restart: on-failure` or systemd can only tell if the process says so. The exit code is
+     * set here rather than left to the entry point because an entry point that catches the rejection
+     * to log it has handled it, and the process would otherwise end with 0. A later `start()` that
+     * logs in -- an entry point retrying -- clears the code again, if this is what set it.
      */
     start(): Promise<void>;
     registerCommands(): Promise<void>;

package/meocord.eslint.cjs

@@ -77,7 +77,7 @@ const specConfig = {
 }
 
 module.exports = [
-  { ignores: ['docs/*', 'build/*', 'lib/*', 'dist/*', 'meocord.config.ts', 'vitest.config.ts'] },
+  { ignores: ['docs/*', 'build/*', 'lib/*', 'dist/*', 'vitest.config.ts'] },
   ...recommendedTypeScriptConfigs,
   specConfig,
   eslintConfigPrettier,

package/meocord.eslint.mjs

@@ -77,7 +77,7 @@ const specConfig = {
 }
 
 export default [
-  { ignores: ['docs/*', 'build/*', 'lib/*', 'dist/*', 'meocord.config.ts', 'vitest.config.ts'] },
+  { ignores: ['docs/*', 'build/*', 'lib/*', 'dist/*', 'vitest.config.ts'] },
   ...recommendedTypeScriptConfigs,
   specConfig,
   eslintConfigPrettier,

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "meocord",
   "description": "Decorator-based Discord bot framework built on discord.js. Brings NestJS-style controllers, dependency injection, guards, and testing utilities to bot development — with a full CLI and TypeScript-first design.",
-  "version": "4.0.0-beta.2",
+  "version": "4.0.0-beta.3",
   "type": "module",
   "engines": {
     "node": ">=22.13"