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
This package uses the ... operator liberally, which means that users need to use a newer version of Node or Babel. Since feathers itself works on older versions of node, I'm wondering if this was a conscious decision on the part of the developers to support only newer versions?
At least, a warning should probably be added to the docs. I haven't yet created a PR for this because I wanted to start a conversation first.
The text was updated successfully, but these errors were encountered:
All our packages are being compiled using Babel and then published which makes them compatible with Node 4+. If you want to use the cloned repository directly you will have to run npm run compile and then require files out of the lib/ folder. This is already done automatically when running npm test.
That's odd. You're right, as I look in the node_modules directory, there aren't any spread operators. But when I added it, my Node v4 server complained with SyntaxError: Unexpected token ... and the cloned repository didn't even exist on that node. Oh well, thanks for the response.
This package uses the
...
operator liberally, which means that users need to use a newer version of Node or Babel. Since feathers itself works on older versions of node, I'm wondering if this was a conscious decision on the part of the developers to support only newer versions?At least, a warning should probably be added to the docs. I haven't yet created a PR for this because I wanted to start a conversation first.
The text was updated successfully, but these errors were encountered: