@therms/react-modules
Advanced tools
This package is for shared React components and utilities that are SPECIFIC
to a [core] module. For example, "authentication" is something core to THERMS webapps
and used by all of the @therms/* npm packages so this package houses the shared
React components, JS utilities, etc..
We do not need to put anything in this package that is only used by 1 webapp or package. If something is not used by more than 1 project, it should only live that project. If a dev later finds out that it needs to use something specific to a THERMS module that has code in another project, then it's a good time to move that code to this package because it will now be needed by more than 1 project.
Any React or JS code that IS NOT SPECIFIC to a core THERMS module and should most likely
live in @therms/react-common.
FAQs
THERMS React components for the primary modules
We found that @therms/react-modules demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
