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

fetch is not defined - maybe your browser targets are not covering everything you need #547

Closed
cah-brian-gantzler opened this issue Aug 8, 2020 · 31 comments · Fixed by #552

Comments

@cah-brian-gantzler
Copy link

cah-brian-gantzler commented Aug 8, 2020

I believe I have tracked the issue down to https://github.com/github/fetch. In version 3.1.1 it used to contain this https://github.com/github/fetch/blob/v3.1.1/fetch.js#L546 but in 3.2.0 it now contains this https://github.com/github/fetch/blob/v3.2.0/fetch.js#L564

Ember-fetch contains this check https://github.com/ember-cli/ember-fetch/blob/master/assets/browser-fetch.js.t#L36. I believe the module body here https://github.com/ember-cli/ember-fetch/blob/master/assets/browser-fetch.js.t#L34 injects the fetch library somehow. Ember-fetch is checking self and I think it now needs to check global maybe. Since this happened so long ago I dont know what dependencies have changed to make it fail for me now, but it failed today for me in multiple unrelated projects.

@mrloop
Copy link

mrloop commented Aug 8, 2020

If your using yarn add this to your package.json

"resolutions": {
  "whatwg-fetch": "3.3.1"
 }

Looks like new release 3.4.0 of whatwg-fetch breaks ember-fetch

@rwjblue
Copy link
Member

rwjblue commented Aug 8, 2020

Hmm, maybe this global:

(function (global) {

Is now conflicting with this?

https://github.com/github/fetch/blob/99b26818147a4288429fcd96421cf038dccbc1ac/fetch.js#L1-L4

@rwjblue
Copy link
Member

rwjblue commented Aug 8, 2020

I did try to see if the tests here would fail with the latest versions of whatwg-fetch, and they do not (#548).

Does anyone have a reproduction?

@RobbieTheWagner
Copy link

All of my addons have started failing with Error: fetch is not defined - maybe your browser targets are not covering everything you need?. What's the workaround?

@RobbieTheWagner
Copy link

This addon docs PR is currently throwing the error ember-learn/ember-cli-addon-docs#495

@RobbieTheWagner
Copy link

I can confirm adding this fixes the issue for addon docs:

"resolutions": {
  "whatwg-fetch": "3.3.1"
 }

Is there a fix we can add to ember-fetch so this is not necessary?

@rwjblue
Copy link
Member

rwjblue commented Aug 8, 2020

Is there a fix we can add to ember-fetch so this is not necessary?

Definitely. Once we know what is actually wrong 😃

We need a repro, and ideally to make this addons test suite fail like what is happening for realz...

@cah-brian-gantzler
Copy link
Author

https://github.com/bgantzler/fetch-app

Just a new application, install ember-fetch, create a controller and import fetch. Will fail when you run the app

@cah-brian-gantzler
Copy link
Author

fails when you run the tests. They are the default blueprint tests unmodified

@cah-brian-gantzler
Copy link
Author

Oh and I resolved to the failing version using

"resolutions": {
  "whatwg-fetch": "3.4.0"
 }

just in case cause I saw a merge of a yarn.lock rollback

@rwjblue
Copy link
Member

rwjblue commented Aug 8, 2020

Just a new application, install ember-fetch, create a controller and import fetch. Will fail when you run the app

Hmm, why aren't our own tests failing here then (if that is all that is needed)?

erikap added a commit to lblod/frontend-loket that referenced this issue Aug 8, 2020
@RobbieTheWagner
Copy link

Just a new application, install ember-fetch, create a controller and import fetch. Will fail when you run the app

Hmm, why aren't our own tests failing here then (if that is all that is needed)?

@rwjblue perhaps importing fetch in tests does not do the same things as importing it in app code?

@RobbieTheWagner
Copy link

Perhaps we should set this addon to explicitly use 3.3.1 until we have a fix?

@cah-brian-gantzler
Copy link
Author

For the simple app I have created above, running the test ember t does fail on the controller

not ok 1 Chrome 84.0 - [145 ms] - Unit | Controller | application: it exists
    ---
        actual: >
            null
        stack: >
            Error: fetch is not defined - maybe your browser targets are not covering everything you need?
                at Module.callback (http://localhost:7357/assets/vendor.js:66720:13)
                at Module.exports (http://localhost:7357/assets/vendor.js:118:32)
                at Module._reify (http://localhost:7357/assets/vendor.js:155:59)
                at Module.reify (http://localhost:7357/assets/vendor.js:142:27)
                at Module.exports (http://localhost:7357/assets/vendor.js:116:10)
                at requireModule (http://localhost:7357/assets/vendor.js:39:18)
                at Class._extractDefaultExport (http://localhost:7357/assets/vendor.js:92885:20)
                at Class.resolveOther (http://localhost:7357/assets/vendor.js:92545:32)
                at Class.resolve (http://localhost:7357/assets/vendor.js:92608:25)
                at resolve (http://localhost:7357/assets/vendor.js:1884:36)
        message: >
            Died on test #1     at Object.<anonymous> (http://localhost:7357/assets/tests.js:15:21)
                at processModule (http://localhost:7357/assets/test-support.js:3894:16)
                at module$1 (http://localhost:7357/assets/test-support.js:3919:4)
                at Module.callback (http://localhost:7357/assets/tests.js:12:21)
                at Module.exports (http://localhost:7357/assets/vendor.js:118:32)
                at requireModule (http://localhost:7357/assets/vendor.js:39:18)
                at TestLoader.require (http://localhost:7357/assets/test-support.js:14364:9)
                at TestLoader.loadModules (http://localhost:7357/assets/test-support.js:14357:14): fetch is not defined - maybe your browser targets are not covering everything you need?
        negative: >
            false
        browser log: |
    ...
ok 2 Chrome 84.0 - [1 ms] - ember-qunit: Ember.onerror validation: Ember.onerror is functioning properly

1..2
# tests 2
# pass  1
# skip  0
# todo  0
# fail  1

@cah-brian-gantzler
Copy link
Author

Oh im sorry. I think I know what you mean. You mean ONLY importing fetch in tests. Yes I believe you may be correct. If has something to do with the loader.

This is the initial post I made in discord help

Uncaught Error: fetch is not defined - maybe your browser targets are not covering everything you need?
    at Module.callback (ember-fetch.js:824)
    at Module.exports (loader.js:106)
    at Module._reify (loader.js:143)
    at Module.reify (loader.js:130)
    at Module.exports (loader.js:104)
    at Module._reify (loader.js:143)
    at Module.reify (loader.js:130)
    at Module.exports (loader.js:104)
    at requireModule (loader.js:27)
    at Class._extractDefaultExport (index.js:397)

@cah-brian-gantzler
Copy link
Author

cah-brian-gantzler commented Aug 9, 2020

I dont know if this helps, but on the repo I posted https://github.com/bgantzler/fetch-app if you switch to the branch acceptance (I just created), the fetch is no longer in the app, so the app no longer fails. It is now only imported in an acceptance test. And it fails there.

@RobbieTheWagner
Copy link

Hmm, I have no idea why it doesn't fail in tests in this repo then. I think we should likely set to 3.3.1 explicitly until someone can figure out the real fix. @rwjblue thoughts on putting that in as a temporary patch?

@cah-brian-gantzler
Copy link
Author

cah-brian-gantzler commented Aug 9, 2020

During this addons test run, the ember-fetch in vendor doesnt have any code where the <%= moduleBody %> is suppose to be
image

When when I run during my apps controller test (master) there is
image

So yea, the test environments they are running in are different

@chancancode
Copy link
Contributor

The tutorial builds are failing as well: https://github.com/ember-learn/super-rentals-tutorial/actions/runs/199896721

@xg-wang
Copy link
Member

xg-wang commented Aug 9, 2020

Created a PR for failing CI.
It seems the self -> global name change Rob mentioned broke ember-fetch

@RobbieTheWagner
Copy link

Nice, thanks @xg-wang! Looking forward to having this merged 😃

@xg-wang
Copy link
Member

xg-wang commented Aug 10, 2020

@rwwagner90 no problem! Just released https://www.npmjs.com/package/ember-fetch/v/8.0.2

@chancancode
Copy link
Contributor

mixonic added a commit to Addepar/ember-table that referenced this issue Aug 10, 2020
Also drop un-used XHR mocking dependencies, and pin a dependency of
ember-cli-addon-docs per
ember-cli/ember-fetch#547 (which could
alternatively be resolved by upgrading ember-cli-addon-docs to ^8.0.2)
mixonic added a commit to Addepar/ember-table that referenced this issue Aug 10, 2020
Also drop un-used XHR mocking dependencies, and pin a dependency of
ember-cli-addon-docs per
ember-cli/ember-fetch#547 (which could
alternatively be resolved by upgrading ember-cli-addon-docs to ^8.0.2)
mixonic added a commit to Addepar/ember-table that referenced this issue Aug 10, 2020
Also drop un-used XHR mocking dependencies, and pin a dependency of
ember-cli-addon-docs per
ember-cli/ember-fetch#547 (which could
alternatively be resolved by upgrading ember-cli-addon-docs to ^8.0.2)
@EugeniaZhang
Copy link

image
"resolutions": {
"whatwg-fetch": "3.4.0"
}
I use this did not resolved the question

@RobbieTheWagner
Copy link

@EugeniaZhang that would not resolve the issue, as 3.4.0 is where the issue began. You would need:

"resolutions": {
  "whatwg-fetch": "3.3.1"
 }

However, version 8.0.2 of ember-fetch has a fix for this issue, so I would recommend updating to 8.0.2.

@iamareebjamal
Copy link

Failing for 8.0.2 as well https://github.com/fossasia/open-event-frontend/pull/4732/files https://travis-ci.com/github/fossasia/open-event-frontend/builds/179380414

@RobbieTheWagner
Copy link

@iamareebjamal maybe try yarn upgrade? If it's failing, something is likely still not using 8.0.2.

bantic added a commit to Addepar/ember-table that referenced this issue Nov 2, 2020
Pin whatwg-fetch dependence to '3.3.1'.

This fixes an error "fetch is not defined - maybe your browser targets are not covering everything you need?"
that shows up when running the tests for the floating dependencies stage.

That error comes from ember-fetch, see ember-cli/ember-fetch#547

Also remove unused ember-ajax and ember-fetch devDependencies
bantic added a commit to Addepar/ember-table that referenced this issue Nov 2, 2020
Pin whatwg-fetch dependence to '3.3.1'.

This fixes an error "fetch is not defined - maybe your browser targets are not covering everything you need?"
that shows up when running the tests for the floating dependencies stage.

That error comes from ember-fetch, see ember-cli/ember-fetch#547
bantic added a commit to Addepar/ember-table that referenced this issue Nov 2, 2020
Pin whatwg-fetch dependence to '3.3.1'.

This fixes an error "fetch is not defined - maybe your browser targets are not covering everything you need?"
that shows up when running the tests for the floating dependencies stage.

That error comes from ember-fetch, see ember-cli/ember-fetch#547
bantic pushed a commit to Addepar/ember-table that referenced this issue Nov 6, 2020
Also drop un-used XHR mocking dependencies, and pin a dependency of
ember-cli-addon-docs per
ember-cli/ember-fetch#547 (which could
alternatively be resolved by upgrading ember-cli-addon-docs to ^8.0.2)
NullVoxPopuli pushed a commit to NullVoxPopuli/ember-table that referenced this issue Feb 2, 2021
Also drop un-used XHR mocking dependencies, and pin a dependency of
ember-cli-addon-docs per
ember-cli/ember-fetch#547 (which could
alternatively be resolved by upgrading ember-cli-addon-docs to ^8.0.2)
johanrd pushed a commit to johanrd/ember-table that referenced this issue Feb 25, 2021
Also drop un-used XHR mocking dependencies, and pin a dependency of
ember-cli-addon-docs per
ember-cli/ember-fetch#547 (which could
alternatively be resolved by upgrading ember-cli-addon-docs to ^8.0.2)
rwjblue added a commit to emberjs/ember-test-helpers that referenced this issue Mar 23, 2021
This was fixed in ember-fetch@8.0.2 but we are stuck using ember-fetch@6
(due to Node version compat). This works around the issue.

See ember-cli/ember-fetch#547 for more
details.
gilest added a commit to adopted-ember-addons/ember-file-upload that referenced this issue Apr 15, 2021
ember-data: Too permissive. The latest version 3.26 was being installed. Incompatible with the existing setup

whatwg-fetch: Incompatible version. Should be cleared up when we next upgrade addon-docs. (ember-cli/ember-fetch#547)
gilest added a commit to adopted-ember-addons/ember-file-upload that referenced this issue Apr 17, 2021
ember-data: Too permissive. The latest version 3.26 was being installed. Incompatible with the existing setup

whatwg-fetch: Incompatible version. Should be cleared up when we next upgrade addon-docs. (ember-cli/ember-fetch#547)
gilest added a commit to adopted-ember-addons/ember-file-upload that referenced this issue Apr 20, 2021
…431)

As sub-dependencies out in the wild have been updated they have caused the "Floating Dependencies" builds to fail.

ember-data: Too permissive. The latest version 3.26 was being installed. Incompatible with the existing addon

whatwg-fetch: Incompatible version. Can be cleared up when we next upgrade addon-docs. (ember-cli/ember-fetch#547)
@tehmaestro
Copy link

I'm using ember-fetch 8.0.4 and still have this issue.

@xg-wang
Copy link
Member

xg-wang commented Apr 20, 2021

@tehmaestro can you paste the output of yarn why whatwg-fetch to tell us what's the versions you're using?

@allthesignals
Copy link

@tehmaestro can you paste the output of yarn why whatwg-fetch to tell us what's the versions you're using?

image

yarn why whatwg-fetch
yarn why v1.22.4
[1/4] 🤔 Why do we have the module "whatwg-fetch"...?
[2/4] 🚚 Initialising dependency graph...
[3/4] 🔍 Finding dependency...
[4/4] 🚡 Calculating file sizes...
=> Found "whatwg-fetch@3.6.2"
info Reasons this module exists

  • "pretender" depends on it
  • Hoisted from "pretender#whatwg-fetch"
  • Hoisted from "ember-fetch#whatwg-fetch"
  • Hoisted from "ember-simple-auth#ember-fetch#whatwg-fetch"
  • Hoisted from "ember-simple-auth-token#ember-fetch#whatwg-fetch"
    info Disk size without dependencies: "72KB"
    info Disk size with unique dependencies: "72KB"
    info Disk size with transitive dependencies: "72KB"
    info Number of shared dependencies: 0
    ✨ Done in 0.87s.

@tehmaestro
Copy link

Hey, turns out I was using ember-simple-auth version 2.1.0, which uses an older version of ember-fetch . I was able to fix the issue by upgrading ember-simple-auth

aatauil added a commit to lblod/frontend-dashboard that referenced this issue Jun 7, 2021
Known issue breaks app but can be resolved by upgrading: ember-cli/ember-fetch#547
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 a pull request may close this issue.

10 participants