You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing from npm, getAppUsage is missing and nowhere to be found in the compiled source code, but when checking the source on github, it can be found inside src/fb.js folder.
NodeJS can run ES6 natively so I'm wondering, why does the npm package contain only the compiled ES5 code?
One quick fix is to install the library directly from github (add the github url directly to package.json), but this is a bit weird as the package is on npm.
The text was updated successfully, but these errors were encountered:
c-dima
changed the title
Method getAppUsage() is missing from npm package
Method getAppUsage() is missing from the npm package
May 22, 2017
getAppUsage is part of the 2.1.0 milestone and hasn't been published to npm which is currently 2.0.0
This library actually uses a number of es7 and unstandardized stage-0 features that NodeJS can't run. NodeJS, also doesn't yet implement all es6 features such as imports. So the code still needs to be transpiled.
Most of the es6 features NodeJS implemented were added in 6.x, this library is compatible back to NodeJS 4.x which was relatively new when 2.0.0 was started. I'll consider updating the minimum NodeJS version to 6.10.x and updating the babel target to 6 when there's a reason to publish a 3.0.0 with breaking changes
When installing from npm, getAppUsage is missing and nowhere to be found in the compiled source code, but when checking the source on github, it can be found inside src/fb.js folder.
NodeJS can run ES6 natively so I'm wondering, why does the npm package contain only the compiled ES5 code?
One quick fix is to install the library directly from github (add the github url directly to package.json), but this is a bit weird as the package is on npm.
The text was updated successfully, but these errors were encountered: