This repository has been archived by the owner on May 9, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Try to use one common node_modules for as many dependencies as possible #45
Labels
Comments
espen42
added a commit
that referenced
this issue
Mar 15, 2021
Builds, but mocha fails at testing:
|
espen42
added a commit
that referenced
this issue
Mar 16, 2021
espen42
added a commit
that referenced
this issue
Mar 17, 2021
espen42
added a commit
that referenced
this issue
Mar 17, 2021
…packages/*. Packages should not run npm install during development - always run gradle npmInstall from the root and keep the root's package.json up to date with all the dependencies: {} under packages/* (dependencies should be both places - but not DEVdependencies). Also, keep the root's package.json up to date with all the DEVdependencies that are used under packages/* (DEVdependencies needed by packages/* should not be declared in the package.json under the specific packages/*, but in the root's package.json).
espen42
added a commit
that referenced
this issue
Mar 17, 2021
espen42
added a commit
that referenced
this issue
Mar 17, 2021
espen42
added a commit
that referenced
this issue
Mar 17, 2021
espen42
added a commit
that referenced
this issue
Mar 18, 2021
…nually verifying the levels and interdependencies
espen42
added a commit
that referenced
this issue
Mar 18, 2021
…is integrated with gradle task npmInstall, so it's better to use that than 'npm i'
espen42
added a commit
that referenced
this issue
Mar 18, 2021
* #45/simplify_node_modules: #45: npm scripts npmLink and npmUnlink handles all crosslinking, and is integrated with gradle task npmInstall, so it's better to use that than 'npm i' Readme: clean command #45: untested, improve versionAndPublish by adding opportunity for manually verifying the levels and interdependencies #45: untested, but versionAndPublish task sequence is tightened and documented. #45 cleanup: remove some deprecated build steps #45: packages/* refactored, so far seems to work: gradlew build, clean, lint and test #45: packages/constants refactored, so far seems to work: gradlew build, clean, lint and test #45: Project root level takes over node_modules, sets up symlinks in packages/*. Packages should not run npm install during development - always run gradle npmInstall from the root and keep the root's package.json up to date with all the dependencies: {} under packages/* (dependencies should be both places - but not DEVdependencies). Also, keep the root's package.json up to date with all the DEVdependencies that are used under packages/* (DEVdependencies needed by packages/* should not be declared in the package.json under the specific packages/*, but in the root's package.json). #45: needed remake after clean. Working with making npm run test:raw work #45: appears to work #45: upgrade mocha. Still doesnt work. #45: trying to make buildcomponents package use dependencies from root node_modules. NPM update
espen42
added a commit
that referenced
this issue
Apr 12, 2021
…s update might not even be the problem.
espen42
added a commit
that referenced
this issue
Apr 19, 2021
* #45/common_node_modules: Docs: updates to build commands Feat: Improved build both locally and in included .gradle files: now more consistent across projects. Feat: included .gradle files parse and react to CLI overrides -Pdev(elopment) and -Pprod(uction) and -Pverbose, making those omittable from react4xp.properties and lowering risk of releasing dev code to prod. Chore: code whitespace Chore: code whitespace Chore: code whitespace #45: NPM updates. Tested this build, did not work. Unclear error, this update might not even be the problem. Dependabot updates. Passes local unit tests.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dependabot runs amok on this project because there's one root project and seven subprojects, each with a package.json of their own and a node_modules. Many of the dependencies are the same. Project maintenance will get MUCH easier (and there will be less dependabot noise) if many of the dependencies can use dependencies from one common node_modules at the root.
The text was updated successfully, but these errors were encountered: