Skip to content

adding support for .cjs file extensions for user function #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

miki725
Copy link

@miki725 miki725 commented Apr 7, 2023

Within ES modules (type is module inside package.json), if you try to either:

require('file')
require('file.js')

it does not allow that as imports should be used within ES modules. The only way to use require() is to explicitly require .cjs file which explicitly indicates that path is a CommonJS file, not ESM:

require('file.cjs')

Issue #, if available:

partly related to #44

Description of changes:

This change allows to require .cjs files when a user function is being searched. I would imagine eventually this library would need to fully support ES modules as per
#44 however this diff will allow people to use lambdas within ES modules if they have .cjs lambda files.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Within ES modules (type is module inside package.json), if you try
to either:

```
require('file')
require('file.js')
```

it does not allow that as imports should be used within ES modules.
The only way to use require() is to explicitly require `.cjs` file
which explicitly insidicates that path is a CommonJS file, not ESM:

```
require('file.cjs')
```

This change allows to require .cjs files when a user function is being
searched. I would imagine eventually this library would need to fully
support ES modules as per
aws#44
however this diff will allow people to use lambdas within ES modules
if they have .cjs lambda files.
@andclt
Copy link
Contributor

andclt commented Jun 28, 2023

Hi @miki725, I think this has been fixed with #70. Feel free to reopen the issue if it is not accurate.

@andclt andclt closed this Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants