Skip to content

fix: move sinon, sinon-mongoose, jest-express, mongodb-memory-server … - #3990

Open
avinxshKD wants to merge 2 commits into
processing:developfrom
avinxshKD:fix/move-test-packages-to-devdependencies
Open

avinxshKD wants to merge 2 commits into
processing:developfrom
avinxshKD:fix/move-test-packages-to-devdependencies

Conversation

@avinxshKD

Copy link
Copy Markdown
Contributor

Fixes #3937

sinon, sinon-mongoose, jest-express, and mongodb-memory-server were sitting in dependencies instead of devDependencies, meaning they get pulled in on every production install for no reason. Moved them where they belong.

Changes:
Moved 4 test-only packages from dependencies to devDependencies in package.json.

I have verified that this pull request:

  • has no linting errors (npm run lint)
  • has no test errors (npm run test)
  • has no typecheck errors (npm run typecheck)
  • is from a uniquely-named feature branch and is up to date with the develop branch.
  • is descriptively named and links to an issue number, i.e. Fixes #3937
  • meets the standards outlined in the accessibility guidelines

@avinxshKD

avinxshKD commented Mar 11, 2026 •

Copy link
Copy Markdown
Contributor Author

Hey @raclim pls take a look, just moved the four packages to devDependencies, alphabetical order preserved.

Also what do you think of this #3922

@yugalkaushik yugalkaushik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@yugalkaushik

yugalkaushik commented Mar 11, 2026 •

Copy link
Copy Markdown
Contributor

I just went through the file and found that jsdom, csslint, htmlhint, jshint can also be moved to devDependencies (yeah, I rechecked they are used, my bad)

@avinxshKD

Copy link
Copy Markdown
Contributor Author

Hey @yugalkaushik thanks for reviewing, also csslint, htmlhint, and jshint are actively used at runtime to lint user code in the editor, not test tooling. jsdom is the same. Moving those would break prod.
Happy to investigate further if needed though

@avinxshKD

Copy link
Copy Markdown
Contributor Author

Hey @raclim pls take a look, when get time thanks

@avinxshKD

Copy link
Copy Markdown
Contributor Author

@raclim can you look at this?

@avinxshKD

Copy link
Copy Markdown
Contributor Author

ptal @doradocodes

@clairep94

clairep94 commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

Hi @avinxshKD thanks for this!
The changes look good but could you re-generate a lock file and include that with the PR?

Make sure to use the npm version for this repo by running nvm use first

@clairep94 clairep94 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

As mentioned we'll need to regenerate the lock file

As an aside, maintainers should add a pre-commit hook or a CI check to flag when lock files are expected to be changed but have not been

@clairep94

Copy link
Copy Markdown
Collaborator

As mentioned we'll need to regenerate the lock file

As an aside, maintainers should add a pre-commit hook or a CI check to flag when lock files are expected to be changed but have not been

cc: @doradocodes, see comment re: lack of check for lockfile changes

@clairep94 clairep94 added the Contributor Follow-up Required Request for changes, or other follow up required. Please see PR comments thread. label Oct 21, 2026

This branch is waiting to be deployed

1 waiting deployment
e2e-tests — 5b2537c9 Waiting Oct 21, 2026 by clairep94 via test-e2e #388
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Contributor Follow-up Required Request for changes, or other follow up required. Please see PR comments thread.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Test-only packages are in production dependencies

3 participants