mailchimp-api | Super-simple , minimum abstraction MailChimp API v3 wrapper | REST library

Note: This question focuses on using a custom HTML form to post new members to a MailChimp list using the MC API; code relating to validation, security, spam/reCaptcha and other important considerations has been omitted. I don't recommend using this code on its own in production.

Original issue: When posting a new 'member' to a MC 'list_id' with their API [using post("lists/$list_id/members")], only two fields, 'status' and 'email_address', are stored, ignoring all the merge_fields I wish to also store.

Solution: 'merge_fields' have to be submitted as an array using the MC API.

In order to solve my issue, I found it useful to experiment a bit directly with the API using curl using GET, as the mailchimp-api library by drewm is great but it hides a bit of the inner workings.

PHP

As far as I can see in the repository for fxp/composer-asset-plugin, it has seen some updates for the property $verbose which is no longer available in current Composer versions. You should update that package.

As it is not listed in your composer.json, some other package seems to require it. And to update the asset plugin, you probably need to update that other package too - check through composer why fxp/composer-asset-plugin which other plugin is responsible for this

try with this format:

First, to answer the question @firebase/app is a module that is part of the Firebase Web SDK (you get it by npm install firebase) and never needs to be manually installed, and should not be installed at all for firebase-admin.

So in a nutshell, here is what's going on with this error, in general: firebase-admin has a dependency called @firebase/database, which is shared with the Firebase Web SDK. A recent release of @firebase/database had some changes that caused it to not work if used with an older version of @firebase/app.

So basically, it should work if you have either (1) no @firebase/app or (2) a current @firebase/app. Your error sounds most likely to be an existing outdated @firebase/app.

I know you said you don't seem to have @firebase/app in your project but since it seems like the most likely cause, I'm wondering if you have it in a parent directory. (It's installed as part of the Firebase Web SDK, as in npm install firebase.) Most firebase functions (if you use firebase init) are set up in a /functions subdirectory of the main project repo, with its own package.json, and the rest of the project is one level up and has another package.json. And that looks like it might be your dir structure?

In that case, running npm ls inside /functions will turn up an empty result, but if you go up to the parent dir (that contains the other package.json), it will show up. Node will go up a level if it doesn't find a package at the current one. See if you can ensure both levels are clean from any @firebase/app, delete both node_modules dirs, reinstall. If you do need it in the top level (for Firebase Web SDK), make sure it is upgraded the most current firebase (7.6.1).

As a last resort, maybe check to see if firebase is npm installed globally somehow.

If you definitely don't have @firebase/app at any level of your project and it's still failing, this is a bug we should look into.

Sorry that's a lot of info! Hope that wasn't too much. TLDR: I think you do probably have @firebase/app in your project root dir? If not, please file an issue on Github.