Skip to content

sqlite: add build option to build without sqlite #58122

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

Closed
wants to merge 4 commits into from

Conversation

mhdawson
Copy link
Member

@mhdawson mhdawson commented May 2, 2025

Distributors of Node.js may want to ship without all of surface area so in some cases
build time options are provided to to that.

I was asked by the RHEL team to add an option to build without sqlite so that have that
flexibility and this PR does that.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/config
  • @nodejs/gyp
  • @nodejs/security-wg
  • @nodejs/sqlite
  • @nodejs/startup

@nodejs-github-bot nodejs-github-bot added lib / src Issues and PRs related to general changes in the lib or src directory. needs-ci PRs that need a full CI run. labels May 2, 2025
@@ -883,6 +885,7 @@ const common = {
hasIntl,
hasCrypto,
hasQuic,
hasSQLite,
Copy link
Member

Choose a reason for hiding this comment

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

Can we move the declaration here?

Copy link
Member Author

Choose a reason for hiding this comment

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

@anonrig can you clarify what you mean on this one?

Copy link
Member

Choose a reason for hiding this comment

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

Instead of having the variable declaration on top of the file, what about:

Suggested change
hasSQLite,
hasSQLite: Boolean(...),

Copy link
Member Author

Choose a reason for hiding this comment

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

That is not consistent with how any of the other ones are done as far as I can see. I was just trying to follow what seems to be existing practice.

Copy link

codecov bot commented May 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.14%. Comparing base (53abd1a) to head (65e8818).
Report is 109 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #58122      +/-   ##
==========================================
- Coverage   90.20%   90.14%   -0.07%     
==========================================
  Files         630      630              
  Lines      186391   186784     +393     
  Branches    36612    36651      +39     
==========================================
+ Hits       168134   168369     +235     
- Misses      11068    11199     +131     
- Partials     7189     7216      +27     
Files with missing lines Coverage Δ
src/node_binding.cc 82.67% <ø> (ø)
src/node_builtins.cc 79.17% <100.00%> (-0.49%) ⬇️
src/node_metadata.cc 91.52% <ø> (ø)

... and 65 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Signed-off-by: Michael Dawson <[email protected]>
@mhdawson
Copy link
Member Author

mhdawson commented May 2, 2025

@anonrig addressed all of your comments except the one I asked for clarification on .

@geeksilva97 geeksilva97 added the request-ci Add this label to start a Jenkins CI on a PR. label May 3, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label May 3, 2025
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

Signed-off-by: Michael Dawson <[email protected]>
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@geeksilva97 geeksilva97 added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label May 7, 2025
@mhdawson mhdawson added the commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. label May 7, 2025
mhdawson added a commit that referenced this pull request May 7, 2025
Signed-off-by: Michael Dawson <[email protected]>
PR-URL: #58122
Reviewed-By: Edy Silva <[email protected]>
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@mhdawson
Copy link
Member Author

mhdawson commented May 7, 2025

Landed in 535c2f7

@mhdawson mhdawson closed this May 7, 2025
targos pushed a commit that referenced this pull request May 16, 2025
Signed-off-by: Michael Dawson <[email protected]>
PR-URL: #58122
Reviewed-By: Edy Silva <[email protected]>
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. lib / src Issues and PRs related to general changes in the lib or src directory. needs-ci PRs that need a full CI run.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants