Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NodeJs v10 support #91

Merged
merged 10 commits into from
Jun 12, 2018
Merged

NodeJs v10 support #91

merged 10 commits into from
Jun 12, 2018

Conversation

mhoeger
Copy link
Contributor

@mhoeger mhoeger commented Jun 8, 2018

Expands supported versions to be 8.x and 10.x

Note: test failures still need to be addressed when using v10.0.0 from this issue: nodejs/node#20258

Must consume latest proto file before pulling into functions-host: Azure/azure-functions-language-worker-protobuf@a42a580

Resolves #66

@mhoeger mhoeger changed the title Node10 support NodeJs v10 support Jun 8, 2018
@mhoeger mhoeger requested a review from pragnagopa June 8, 2018 22:27
tsconfig.json Outdated
@@ -4,6 +4,7 @@
"target": "es6",
"noImplicitAny": false,
"strict": true,
"strictNullChecks": false,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we keep the default as it might be safer?

Copy link
Member

@pragnagopa pragnagopa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Just a comment on the null checks. Can you please send a PR to java worker repo and also open an issue in python worker repo as a heads up that breaking change is coming in

@mhoeger mhoeger requested a review from paulbatum June 11, 2018 21:47
@paulbatum
Copy link
Member

Just curious - why does the upgrade to node 10 result in a breaking change in the proto file?

@mhoeger
Copy link
Contributor Author

mhoeger commented Jun 12, 2018

We need to upgrade protobufjs to be able to use node 10, and upgrading protobufjs resulted in a few breaking changes. One of them is that we used to call the package "FunctionRpc" and the service "FunctionRpc" in our proto file. This now doesn't compile from type errors due to the naming conflict

@paulbatum
Copy link
Member

got it, thanks!

@mhoeger mhoeger merged commit 03ae731 into Azure:dev Jun 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants