apollo-client: Cannot set property default of #<Object> which has only a getter

This should be fixed in apollo-boost@0.4.1 (just released).

+33

benjamn on Jun 4, 2019

Temporary workaround import ApolloClient from "apollo-boost/lib/index";

+29

vomchik on May 24, 2019

I am having this issue as well using 0.4.0. Reverting back to 0.3.1 resolved my issue for the time being.

+15

creekdrops on May 22, 2019

This appears to be an upstream bug in the Rollup CommonJS output for apollo-boost/lib/bundle.cjs.js.

In order to compile

export * from "apollo-client"
export default class DefaultClient { ... }

Rollup generates the following code:

var ApolloClient__default = require('apollo-client');

Object.keys(ApolloClient__default).forEach(function (key) {
    Object.defineProperty(exports, key, {
        enumerable: true,
        get: function () {
            return ApolloClient__default[key];
        }
    });
});

exports.default = DefaultClient;

However, because apollo-client also has a default export, that default export is mistakenly defined on exports in the forEach loop by Object.defineProperty in a way that cannot simply be overridden by the exports.default = DefaultClient assignment. That’s why you’re seeing the error

Cannot set property default of #<Object> which has only a getter

According to the ECMAScript specification, the default export should actually be excluded when doing export * from "apollo-client". When I first learned about this gotcha, it surprised me too, but the TC39 committee (including myself) have reached a firm consensus on this behavior, and Rollup is violating the specification by copying over all exported properties of apollo-client.

I will open other issues in the appropriate places, but I wanted to give everyone an update here first.

+11

benjamn on May 24, 2019

This should be fixed in apollo-boost@0.4.1 (just released).

I just installed 0.4.1 and it fixed the issue (Y)

+6

DarkSmile92 on Jun 4, 2019

I’m having a similar issue with Next.js & Apollo Client configuration ~ next-apollo, reverting back to old versions solved my issues for now.

+4

lastnamearya on May 22, 2019

I had the exact same issue with 0.4.0, then I downgraded to 0.3.1 then everything worked fine

+2

kingRayhan on May 24, 2019

Had the issue with apollo-boost -> 0.4.0 and went back to 0.3.1 per @musemind’s post and it fixed the issue. I tried multiple config options, and even no config at all and the issue still remained.

+2

drewbietron on May 23, 2019

Just to expand on what @mattschoch suggested above, it might be a good idea to use ~ instead of ^, since ^2.5.1 matches 2.6.1, but ~2.5.1 only matches 2.5.x versions.

+1

benjamn on Jun 6, 2019

Also having this issue with new ApolloClient() with an TypeScript + ReactNative + Expo setup. The import import ApolloClient from 'apollo-boost' alone does not cause any error. Reverting to 0.3.1 does not help for me. Perhaps it’s an issue with TypeScript imports.

Using the isolated packages / imports works for me:

import { ApolloClient } from 'apollo-client'
import { InMemoryCache } from 'apollo-cache-inmemory'
import { HttpLink } from 'apollo-link-http'

const client = new ApolloClient({
  cache: new InMemoryCache(),
  link: new HttpLink({
    uri: '...'
  })
})

+1

musemind on May 22, 2019

apollo-client: Cannot set property default of #

About this issue

Commits related to this issue

Most upvoted comments