fix(github-actions): improve error logging and fix ESM node resolution

We recently prioritized `module` over `main` but this results in browser
code being prioritized sometimes. We revert that change and keep the
original/default ESBuild main field order.

This unveils an issue with `jsonc-parser` though- which ships an UMD
file for `main` that cannot be bundled. We can work around this by
processing `jsonc-parser`'s ESM output directly and then using that
instead of leaving resolution to ESBuild for this package.

There is an issue for this being tracked: microsoft/node-jsonc-parser#57

Author: devversion

.github/local-actions/changelog/main.js

@@ -29,7 +29,6 @@ def esbuild_esm_bundle(name, **kwargs):
 
     args = dict(
         resolveExtensions = [".mjs", ".js", ".json"],
-        mainFields = ["module", "main"],
         outExtension = {".js": ".mjs"},
         # Workaround for: https://github.com/evanw/esbuild/issues/1921.
         banner = {

bazel/esbuild/index.bzl

@@ -93,7 +93,7 @@ class CommitMessageBasedLabelManager {
 // to prevent the action from actually running in a fork of a repository with this action set up.
 if (context.repo.owner === 'angular') {
   CommitMessageBasedLabelManager.run().catch((e: Error) => {
-    core.error(e);
+    console.error(e);
     core.setFailed(e.message);
   });
 } else {

github-actions/commit-message-based-labels/lib/main.ts

@@ -201,7 +201,7 @@ async function main(): Promise<void> {
     }
   } catch (err: any) {
     core.setOutput('result', ActionResult.failed);
-    core.error(err);
+    console.error(err);
     core.setFailed(err.message);
   }
 }

github-actions/commit-message-based-labels/main.js

@@ -97,6 +97,6 @@ async function findExistingTestStatus(
 }
 
 main().catch((e: Error) => {
-  core.error(e);
+  console.error(e);
   core.setFailed(e.message);
 });