package.json dependancies seem off and bloated. about facebook-nodejs-business-sdk

[michaelwclark]

I'm going to do a PR hopefully today with the fix. Also in the likely and common event that it takes 6+ weeks to I'll do a fork of this. I don't want to do that, but at this point the whole community is struggling with this issue and we need to keep it moving forward.

[codytwinton]

We have merged #73 internally and it should be available on the next release.

[bertero]

Update:
I manually removed the phantomjs-prebuilt and unicode-5.2.0 modules and then normally retrieved and updated campaigns and adSets data.

Something doesn't seem right here guys...

[yassera2]

I'm facing the same issue. Specifically, we're using AWS lambda and the node modules are exceeding the package size limit because of those extra dependencies.

[mledom]

Agreed, we just ran npm install and noticed phantomJS building downloaded. Its being included from glow-flowtype. I agree with @michaelwclark seems like there are a lot of deps that should be moved to devDep.

[bertero]

The size of the dependencies is simply huge... I have a 450M project, where more than 300M is only because of facebook-nodejs-business-sdk. Is this really correct?

I don't know if this is the case to open some issue, but it is unavailable for me to keep using it... Does someone know how to make it smaller?

[mledom]

I'm in the same boat as @yassera2, I'm having trouble deploying to AWS Lambda. I was able to remove the two that @bertero mentioned (thanks!) Seems like there is some optimization that could take place.

[michaelwclark]

@mledom npm i @denimlabs/facebook-nodejs-business-sdk https://github.com/denimlabs/facebook-nodejs-business-sdk is our active fork. I've been releasing a few times a week so far. Feel free to use that. It reduced our build size signifigantly. Iv'e also added some features and squashed a few bugs. The PR #73
was approved to reduce size, but idk the release schedule with these guys maybe @codytwinton can shed some light on that?

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.