Unable to Import buttercms

[spencerkordecki]

Hello!

We're currently using v2.0.1 of buttercms in our project, but when we try to update to v2.3.1 to get the V2 types, we run into a similar issue to the one here: #105

We are using a standard React app with Express, running Node v20.12.0 at the moment.

TypeError: (0 ,_buttercms.default) is not a function

Let me know if there's any other info I can provide.

import Butter from 'buttercms';

// ...

const butter = Butter(config.BUTTER_CMS_TOKEN) // BUTTER_CMS_TOKEN is mapped to a string

[ViolanteCodes]

@spencerkordecki We had one of our JS devs test and this was their report:

I set up a JS and TS project on Node 20.12.0, using React. I tested both version of buttercms - 2.0.1 and 2.3.1. In both cases importing Butter works correct. No issue. I spot just one difference in versions - exactly in retrieving page data:
2.0.1 -> response.data
2.3.1 -> response.data.data
to get the same results
but it's not related to issue reported by user. 

Are you able to give us some more information on your setup or implementation so that we can better try to reproduce this error? Thank you!

cc @LenardMarcin @marcin-pece for tracking purposes

[spencerkordecki]

Sure! So for some more context, we're currently on 2.0.1. I can upgrade to 2.1.2 as the latest possible, but 2.1.3 and beyond crashes with that same error I mentioned in the original message.

I tried changing our middleware to look at response.data.data, but it doesn't even get far enough to look at that and immediately crashes out with the TypeError: (0 , _buttercms.default) is not a function error.

This is a server-side rendered application using Express v5, React v18, and Webpack 5; nothing fancy there.

[spencerkordecki]

@ViolanteCodes @LenardMarcin @marcin-pece any updates on this? The issue outlined above blocks us from upgrading to anything past 2.1.2, and with V2 support ending next month, we'll need to get this resolved to update in time.

[ViolanteCodes]

@spencerkordecki we have a PR going through the review and testing process right now: #117.

Just to cover all our bases, are you able to pull down that PR and verify it resolves your issue?

[spencerkordecki]

@ViolanteCodes sorry I didn't get a chance to pull down the PR before it got merged in, but pulled down the latest release and it's working perfectly now, thank you! this issue can be closed.

[ViolanteCodes]

@spencerkordecki glad to hear it 🙌 🙌