Merge package jsons #11419

happythenewsad · 2024-01-16T19:45:30Z

WHAT

Merges client/package.json into package.json

having two package.jsons is tech debt: it is extra complication with no added value.

it requires managing two separate node_modules caches
it prevents upgrading to npm 8.x in local environments slack
it maintains repetitive scripts (example: npm run jest is first evaluated in package.json, then delegated to client/package.json

(If applicable. Also, please censor any sensitive data)

PR Checklist	Your Answer
Have you added and/or updated tests?	(The answer should mostly be 'YES'. If you answer 'NO', please justify.)
Have you deployed to Staging?	(Possible answers: YES, Not yet - deploying now!, NO - non-app change, NO - tiny change)
Self-Review: Have you done an initial self-review of the code below on Github?
Spec Review: Have you reviewed the spec and ensured this meets requirements and/or matches design mockups?	(N/A or Yes)

happythenewsad · 2024-01-16T20:01:17Z

services/QuillLMS/babel.config.cjs

@@ -0,0 +1,6 @@
+module.exports = {


babel.config.cjs is not preferred over .babelrc

Source: jestjs/jest@1818d84#diff-04c6e90faac2675aa89e2176d2eec7d8

Peter Kong added 2 commits January 16, 2024 10:53

wip

7fc6446

use bable.config.js instead of babelrc; most jests passing

145a15e

happythenewsad commented Jan 16, 2024

View reviewed changes