[GH-ISSUE #241] ReferenceError: fetch is not defined #7486

Closed
opened 2026-04-21 19:25:14 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @techmobify on GitHub (Nov 10, 2023).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/241

While fetching Instagram data, I got this error:

ReferenceError: fetch is not defined
at request (/cobalt/src/modules/processing/services/instagram.js:20:18)
at getPost (/cobalt/src/modules/processing/services/instagram.js:51:23)
at default (/cobalt/src/modules/processing/services/instagram.js:147:24)
at default (/cobalt/src/modules/processing/match.js:112:27)
at getJSON (/cobalt/src/modules/api.js:32:22)
at /cobalt/src/core/api.js:100:31
at Layer.handle [as handle_request] (\cobalt\node_modules\express\lib\router\layer.js:95:5)
at next (\cobalt\node_modules\express\lib\router\route.js:144:13)
at Route.dispatch (\cobalt\node_modules\express\lib\router\route.js:114:3)
at Layer.handle [as handle_request] (\cobalt\node_modules\express\lib\router\layer.js:95:5)

Originally created by @techmobify on GitHub (Nov 10, 2023). Original GitHub issue: https://github.com/imputnet/cobalt/issues/241 While fetching Instagram data, I got this error: ReferenceError: fetch is not defined at request (/cobalt/src/modules/processing/services/instagram.js:20:18) at getPost (/cobalt/src/modules/processing/services/instagram.js:51:23) at default (/cobalt/src/modules/processing/services/instagram.js:147:24) at default (/cobalt/src/modules/processing/match.js:112:27) at getJSON (/cobalt/src/modules/api.js:32:22) at /cobalt/src/core/api.js:100:31 at Layer.handle [as handle_request] (\cobalt\node_modules\express\lib\router\layer.js:95:5) at next (\cobalt\node_modules\express\lib\router\route.js:144:13) at Route.dispatch (\cobalt\node_modules\express\lib\router\route.js:114:3) at Layer.handle [as handle_request] (\cobalt\node_modules\express\lib\router\layer.js:95:5)
Author
Owner

@wukko commented on GitHub (Nov 10, 2023):

you need to update node.js on your machine to latest LTS or newer. read requirements in docs next time.

<!-- gh-comment-id:1805128074 --> @wukko commented on GitHub (Nov 10, 2023): you need to update node.js on your machine to latest LTS or newer. read requirements in docs next time.
Sign in to join this conversation.