Skip to content

v8: move process.binding('v8') to internalBinding - #22288

Closed
jasnell wants to merge 1 commit into
nodejs:masterfrom
jasnell:v8-internal-binding
Closed

v8: move process.binding('v8') to internalBinding#22288
jasnell wants to merge 1 commit into
nodejs:masterfrom
jasnell:v8-internal-binding

Conversation

@jasnell

Copy link
Copy Markdown
Member

Refs: #22160

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@jasnelljasnell added the semver-major PRs that contain breaking changes and should be released in the next major version. label Aug 12, 2018
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-botnodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. v8 engine Issues and PRs related to the V8 dependency. labels Aug 12, 2018
@BridgeAR
BridgeAR requested a review from a teamAugust 13, 2018 00:32
@BridgeAR

Copy link
Copy Markdown
Member

@BridgeARBridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Aug 13, 2018

@jdaltonjdalton left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Holding removals until migration is ironed out

@jdaltonjdalton left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

[wrong button]

@jasnell

Copy link
Copy Markdown
MemberAuthor

@jdalton ... The require('v8') and process.binding('v8') bindings are explicitly not covered by existing semver rules.

See https://nodejs.org/dist/latest-v10.x/docs/api/v8.html#v8_v8:

The APIs and implementation are subject to change at any time.

Therefore, this PR should not be blocked by the transition discussion.

@jdalton

Copy link
Copy Markdown
Member

Therefore, this PR should not be blocked by the transition discussion.

I'd dig it if we could get a rough wag at usage before skipping deprecation processes.

@jasnell

Copy link
Copy Markdown
MemberAuthor

Technically the v8 module is not covered by the normal deprecation processes so they're not being skipped. However, once #22269 lands, I can add 'v8' to the whitelist for the time being.

@jasnell
jasnellforce-pushed the v8-internal-binding branch from 01a0230 to a2d45fbCompareAugust 15, 2018 02:26
@jasnell

Copy link
Copy Markdown
MemberAuthor

@jdalton ... added process.binding('v8') to the fallthrough whitelist

@jasnell

Copy link
Copy Markdown
MemberAuthor

@jasnell

Copy link
Copy Markdown
MemberAuthor

ping @nodejs/tsc

@jasnell

Copy link
Copy Markdown
MemberAuthor

@jasnell

Copy link
Copy Markdown
MemberAuthor

Another CI failure in linux-containered: https://ci.nodejs.org/job/node-test-commit-linux-containered/6330/

@jasnell
jasnellforce-pushed the v8-internal-binding branch 2 times, most recently from 8840799 to 9a0dcd0CompareAugust 16, 2018 21:27
@jasnell

Copy link
Copy Markdown
MemberAuthor

@Trott

Copy link
Copy Markdown
Member

@jasnell

Copy link
Copy Markdown
MemberAuthor

@jasnell
jasnellforce-pushed the v8-internal-binding branch from 9a0dcd0 to e0a0987CompareAugust 18, 2018 13:33
@jasnell

Copy link
Copy Markdown
MemberAuthor

@jasnell

Copy link
Copy Markdown
MemberAuthor

Trying arm fanned again because of an unrelated failure... https://ci.nodejs.org/job/node-test-commit-arm-fanned/3012/

@jasnell

jasnell commented Aug 18, 2018

Copy link
Copy Markdown
MemberAuthor

@jasnell
jasnellforce-pushed the v8-internal-binding branch from e0a0987 to c5a3d31CompareAugust 18, 2018 20:13
@jasnell

Copy link
Copy Markdown
MemberAuthor

@Trott

Copy link
Copy Markdown
Member

jasnell added a commit to jasnell/node that referenced this pull request Aug 18, 2018
PR-URL: nodejs#22288
Refs: nodejs#22160
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com>
Reviewed-By: John-David Dalton <john.david.dalton@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Yuta Hiroto <hello@hiroppy.me>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
@jasnell

Copy link
Copy Markdown
MemberAuthor

Landed in 892932f

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.c++Issues and PRs that require attention from people who are familiar with C++.semver-majorPRs that contain breaking changes and should be released in the next major version.v8 engineIssues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

13 participants

@jasnell@nodejs-github-bot@BridgeAR@jdalton@Trott@addaleax@TimothyGu@cjihrig@maclover7@hiroppy@joyeecheung@devsnek@trivikr