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
The reason tonic uses node 0.12 is because the engines variable isn't set in parse-server's package.json. If you set engines: { node: ">= 4" } then Tonic will appropriately choose node 4 and the syntax error won't happen. Given that the package expects ES6 to be natively present this seems like the right engine. An alternative is to have a pre-publish step that babel-ifies the code so that it can work on any node.
Thanks,
Francisco
The text was updated successfully, but these errors were encountered:
Was taking a look at this: #4
The reason tonic uses node 0.12 is because the engines variable isn't set in parse-server's package.json. If you set engines: { node: ">= 4" } then Tonic will appropriately choose node 4 and the syntax error won't happen. Given that the package expects ES6 to be natively present this seems like the right engine. An alternative is to have a pre-publish step that babel-ifies the code so that it can work on any node.
Thanks,
Francisco
The text was updated successfully, but these errors were encountered: