-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
request
is deprecated
#7
Comments
DanielHabenicht
added a commit
that referenced
this issue
Jan 9, 2022
fixes `request` is deprecated #7 BREAKING CHANGE: use `fetchOptions` instead of `request` in you config
DanielHabenicht
added a commit
that referenced
this issue
Jan 9, 2022
fixes `request` is deprecated #7 BREAKING CHANGE: use `fetchOptions` instead of `request` in you config
DanielHabenicht
added a commit
that referenced
this issue
Jan 9, 2022
fixes `request` is deprecated #7 BREAKING CHANGE: use `fetchOptions` instead of `request` in you config
github-actions bot
pushed a commit
that referenced
this issue
Jan 9, 2022
# [2.0.0](v1.1.4...v2.0.0) (2022-01-09) ### Bug Fixes * Rename Notifications ([869e182](869e182)) * use node-fetch instead of request ([75cd82f](75cd82f)), closes [#7](#7) ### BREAKING CHANGES * use `fetchOptions` instead of `request` in you config * rename notifications to better resemble that they could also be POST or other requests. MMM_JSON_GET_REQUEST > MMM_JSON_REQUEST MMM_JSON_GET_RESPONSE > MMM_JSON_RESPONSE
fixed in #8 |
Thanks for poking me about it. It was already outdated when I create the module but I couldn't find a good alternative at that point in time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The
request
library is deprecated and no longer supported.Additional context
request/request#3142
The text was updated successfully, but these errors were encountered: