GV14982 / async-airtable

A lightweight npm package to handle working with the Airtable API.
https://www.npmjs.com/package/asyncairtable
MIT License
54 stars 5 forks source link

ReferenceError: define is not defined #38

Closed stevenpersia closed 3 years ago

stevenpersia commented 3 years ago

Describe the bug After install and import, I've got this error. I've tried on multiple node version.

To Reproduce Here a link to runkit : https://runkit.com/stevenpersia/referenceerror-define-is-not-defined

Expected behavior Except to try your amazing tool :smiley:

Screenshots image

GV14982 commented 3 years ago

Hi Steven, thanks for submitting this issue.

This is actually an issue with how we are compiling the the package currently. This is will be fixed in the next release. For now, if you just want to try using asyncairtable@next (which is the release from the develop branch) and let me know if that helps.

avanavana commented 3 years ago

I am having the same issue. Figured it was because it needs to be loaded with amd-loader, so I added that, but then I received this error:

Screen Shot 2020-12-14 at 4 20 48 PM

Shame, because I really would love to use this module instead of the regular Airtable API.

I also tried using this guy's define shim for nodejs, and I got an error: "buildOpts is not defined".

Edit: tried the dev release. you mentioned and got the following error: Screen Shot 2020-12-14 at 4 27 43 PM

and on RunKit.

Screen Shot 2020-12-14 at 4 34 18 PM

GV14982 commented 3 years ago

Hi @avanavana, thanks for reporting the issue. I'll see if I can get a release setup tonight, as it seems that runkit does not let you use tags when downloading packages.

stevenpersia commented 3 years ago

I've got same issue as above when I use asyncairtable@next on local node project : AsyncAirtable is not a constructor.

avanavana commented 3 years ago

Hi @avanavana, thanks for reporting the issue. I'll see if I can get a release setup tonight, as it seems that runkit does not let you use tags when downloading packages.

Thanks, I'm in no rush, but I am glad you are working on this because when it's ready I will be so glad to switch over to async and clean my code up.

This wasn't just runkit- on my local node project I tried asyncairtable@next (the second to last screenshot) too.

GV14982 commented 3 years ago

Can you test asyncairtable@next on a local node environment just to be sure it works? If it does I'll do a regular release so it can be used correctly on tools like runkit.

stevenpersia commented 3 years ago

It works great on my side ! Thank you for your reactivity :tada: :+1:

GV14982 commented 3 years ago

Perfect! I will get a release together for tonight. Please let me know any thoughts you have and if this is missing any features you might want/need!

avanavana commented 3 years ago

Can you test asyncairtable@next on a local node environment just to be sure it works? If it does I'll do a regular release so it can be used correctly on tools like runkit.

Sorry, haven't had time to look at this until now. Works like a charm. Thanks so much for this!

GV14982 commented 3 years ago

Just an FYI, I just released 1.2.4 so now it is available on both RunKit and via CDN's such as UNPKG and jsDelivr 🙂