Use package entry points for conditional exports between cjs/esm

[matux]

Description of the change

This PR fixes more issues around import and require discrepancies by introducing a modern way to define package entry points, called Conditional Exports which were introduced 6 years ago in Node 12.7.0.

Conditional Exports replace the legacy main, browser and module fields providing fine-grained control over what files can be imported from our package and how.

This change was prompted by the universal-node example which wouldn't be able to require('rollbar') without suffixing .default to it. This is because node looked into our package.json and resolved to use our main field which points to an es module.

Note

Before Conditional Exports, packages had to expose main and rely on hacks like pkg.module (non-standard) for ESM builds. Conditional exports made dual packages clean and official.

See the official Proposal for Bare Module Specifier Resolution in node.js

The introduced changes override main, browser and module fields for all nodes >= 12.7.0, and any node < 12 will fallback to the older fields. I'm keeping everything to maximize compatibility.

---

Important

With this change I can confirm that all examples that integrate rollbar through their package.json file are 100% working.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Maintenance
• New release

Related issues

• SDK-518/make-sure-all-sdk-examples-work-properly
• SDK-521/use-package-entry-points-for-conditional-exports-between-cjsesm

[Copilot]

Pull Request Overview

This PR modernizes the package entry point configuration by implementing Node.js Conditional Exports to resolve import/require discrepancies between CommonJS and ES modules. The change replaces reliance on legacy fields with a structured approach that provides different module formats based on the runtime environment and import method.

• Introduces conditional exports configuration in package.json for Node.js >= 12.7.0
• Creates a CommonJS wrapper file to bridge ES modules for require() usage
• Updates the main field to point to the new CommonJS wrapper

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	Adds exports field with conditional entry points and updates main field
src/server/rollbar.cjs	New CommonJS wrapper that re-exports the default export from the ES module

[Copilot]

This line could fail if './rollbar.js' doesn't have a default export or if the module loading fails. Consider adding error handling or validation to provide clearer error messages when the ES module cannot be loaded or lacks a default export.

Suggested change

	module.exports = require('./rollbar.js').default;
	try {
	const rollbarModule = require('./rollbar.js');
	if (!rollbarModule || !rollbarModule.default) {
	throw new Error("The './rollbar.js' module does not have a default export.");
	}
	module.exports = rollbarModule.default;
	} catch (error) {
	throw new Error(`Failed to load './rollbar.js': ${error.message}`);
	}