Skip to content
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.

Fix install / build by using latest LTS node #364

Merged
merged 3 commits into from
May 10, 2019

Conversation

tiffon
Copy link
Member

@tiffon tiffon commented May 10, 2019

Which problem is this PR solving?

Fix #363.

Short description of the changes

Use the current LTS version of node (see releases).

This adds adds a package-lock.json and causes two prettier formatting changes.

@tiffon tiffon changed the title Fix #363 by using latest LTS node Fix install / build by using latest LTS node May 10, 2019
@codecov
Copy link

codecov bot commented May 10, 2019

Codecov Report

Merging #364 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #364   +/-   ##
=======================================
  Coverage   99.12%   99.12%           
=======================================
  Files          44       44           
  Lines        1717     1717           
  Branches      337      337           
=======================================
  Hits         1702     1702           
  Misses         15       15
Impacted Files Coverage Δ
src/configuration_env.js 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a12692c...b4b2175. Read the comment docs.

Copy link
Collaborator

@everett980 everett980 left a comment

Choose a reason for hiding this comment

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

LGTM aside from one dependency question.

General question that doesn't need to be addressed in this PR:
some of these changes seem stylistic, is it worth bolstering our eslint / prettier usage for this repo?

package.json Outdated
"opentracing": "^0.13.0",
"uuid": "^3.2.1"
"prom-client": "^11.0.0",
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't see this dependency in use in the PR, is it required by using a different node version?

Copy link
Member Author

@tiffon tiffon May 10, 2019

Choose a reason for hiding this comment

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

Awesome catch! npm now saves packages, by default!

npm install saves any specified packages into dependencies by default.
– npm help install

package.json Outdated
"opentracing": "^0.13.0",
"uuid": "^3.2.1"
"prom-client": "^11.0.0",
Copy link
Member

Choose a reason for hiding this comment

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

this isn't a required runtime dependency

Copy link
Member Author

Choose a reason for hiding this comment

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

The newer version of npm installs by default. This has been removed and the Makefile updated to not save the dependency when it's installed.

console.warn(
`You are using deprecated env variable ${env}. Use ${
deprecatedEnvVars[env]
} instead. \nDeprecated env variable will be removed in the next major release (4.x.x)`
Copy link
Member

Choose a reason for hiding this comment

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

this split doesn't look right

Copy link
Member Author

@tiffon tiffon May 10, 2019

Choose a reason for hiding this comment

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

It's automatic formatting via prettier. I suggest we leave as is.

@yurishkuro yurishkuro merged commit 5c89fa5 into jaegertracing:master May 10, 2019
Iuriy-Budnikov pushed a commit to agile-pm/jaeger-client-node that referenced this pull request Sep 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

make build-node fails on master
3 participants