feat: add support for commonjs loaders#2380
Open
esatterwhite wants to merge 10 commits intoactions:mainfrom
Open
feat: add support for commonjs loaders#2380esatterwhite wants to merge 10 commits intoactions:mainfrom
esatterwhite wants to merge 10 commits intoactions:mainfrom
Conversation
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
When this package was converted to esm, it only defined an `import` declaration in the package manifest making it impossible to load via commonjs / require. Nodejs 22.12.0 added support for loading ecmascript modules via require and commonjs modules via import. As long as the file extension is `.js` and there is no top-level await, the same code can be loaded by either mechanism. This change adds the `require` and `default` decarations to the `exports` section of package.json making it possible for this package to be used in either project type. Fixes: actions#2294
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When this package was converted to ecmascript modules, it only defined an
importdeclaration in the package manifest making it impossible to load via
commonjs / require. Nodejs 22.12.0 added support for loading ecmascript
modules via require and commonjs modules via import. As long as the file
extension is
.jsand there is no top-level await, the same code can beloaded by either mechanism. This change adds the
requireanddefaultdeclarations to the
exportssection of package.json making it possiblefor this package to be used in either project type.
Fixes: #2294