Skip to content
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

webpack issue #249

Closed
Lazyshot opened this issue May 25, 2020 · 2 comments
Closed

webpack issue #249

Lazyshot opened this issue May 25, 2020 · 2 comments

Comments

@Lazyshot
Copy link

Lazyshot commented May 25, 2020

Currently there is an outstanding issue with webpack and node-fetch:

node-fetch/node-fetch#450

The suggested workaround is var fetch = require("node-fetch").default; instead of just var fetch = require('node-fetch')

Also saw this was mentioned in #227 and #192

My specific reason for this issue is because it is required to use webpack for netlify lambda functions and a couple libraries I rely on are upstream dependents.

@d-fischer
Copy link
Contributor

#239 might have fixed this; care to confirm?

@Lazyshot
Copy link
Author

Lazyshot commented Jun 2, 2020

Strangely enough, you own my dependency (https://github.com/d-fischer/twitch), so I'll take your word for it and move over there. Appreciated.

@Lazyshot Lazyshot closed this as completed Jun 2, 2020
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

No branches or pull requests

2 participants