fix: __esModule is missing from published @babel/parser (#15935)

Co-authored-by: Nicolò Ribaudo <nicolo.ribaudo@gmail.com>

Gulpfile.mjs

@@ -509,6 +509,7 @@ function buildRollup(packages, buildStandalone) {
 
         const outputFile = path.join(src, dest, filename || "index.js");
         await bundle.write({
+          esModule: true,
           file: outputFile,
           format,
           name,
@@ -557,6 +558,7 @@ function buildRollup(packages, buildStandalone) {
         await bundle.write({
           file: outputFile.replace(/\.js$/, ".min.js"),
           format,
+          esModule: true,
           interop: "compat",
           name,
           sourcemap: sourcemap,

packages/babel-parser/src/index.ts

@@ -20,7 +20,6 @@ import {
   tt as internalTokenTypes,
   type InternalTokenTypes,
 } from "./tokenizer/types.ts";
-import "./tokenizer/context.ts";
 
 import type { Expression, File } from "./types.ts";
 

packages/babel-parser/test/commonjs.bundled.js

@@ -0,0 +1,12 @@
+import { itNoESM, itESM, commonJS } from "$repo-utils";
+
+describe("commonjs bundle", () => {
+  itESM("dummy", () => {});
+
+  itNoESM("has an __esModule export", () => {
+    const { require } = commonJS(import.meta.url);
+
+    // This will require the bundle when running the tests when publishing
+    expect(require("../lib/index.js").__esModule).toBe(true);
+  });
+});