fetch is not a function. #131
Conversation
|
@JJ-Kidd thanks for the PR. I'm not opposed to merging this as is, but I'm keen to understand why it's required. Do you have any references or documentation on the "loose import" issue with Webpack? I have previously used this package on AWS Lambda without issue, though I don't remember using Webpack, so I guess Webpack is doing something weird... |
|
Hah I found the history. From my initial reading of that issue it sounds like a bug with Webpack that shouldn't have been closed, and that library maintainers shouldn't be expected to account for. I'm going to begrudgingly merge this and add a comment detailing why it exists though. Thanks! |
|
Thanks @callum-oakley. Any idea when I'll be able to grab this as a tagged version? |
|
I'll push a new release just as soon as the tests have passed on master, watch this space :) |
|
Published as 4.0.2 |
What
Adding .default to the import of node-fetch
Why
When this package is deployed as part of a Lambda function it is unable to find fetch, this is because it is loosely imported
Issue
#130