Gathering detailed insights and metrics for @teamteanpm2024/exercitationem-veritatis-ipsa
Gathering detailed insights and metrics for @teamteanpm2024/exercitationem-veritatis-ipsa
Installations
npm install @teamteanpm2024/exercitationem-veritatis-ipsaDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
20.12.2
NPM Version
10.5.0
Score
58.5
Supply Chain
41.5
Quality
79.8
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Contributors
1
Download Statistics
Total Downloads
416
Last Day
1
Last Week
3
Last Month
15
Last Year
416
Maintainers
1
Package Meta Information
Latest Version
1.0.5
Package Id
@teamteanpm2024/exercitationem-veritatis-ipsa@1.0.5
Unpacked Size
24.62 kB
Size
9.34 kB
File Count
10
NPM Version
10.5.0
Node Version
20.12.2
Publised On
29 Apr 2024
Total Downloads
Cumulative downloads
Total Downloads
416
Last day
0%
1
Compared to previous day
Last week
-50%
3
Compared to previous week
Last month
36.4%
15
Compared to previous month
Last year
0%
416
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
37
@libphamton/chatfanpage@libphamton/fb-group@oraliepham/api-chat-fanpage-facebook@oraliepham/api-facebooknew@teamteanpm2024/aperiam-dolor-aliquid@teamteanpm2024/aperiam-fugit-error@teamteanpm2024/aperiam-similique-soluta@teamteanpm2024/architecto-alias-quod@teamteanpm2024/asperiores-atque-fugit@teamteanpm2024/aut-voluptatum-vero@teamteanpm2024/beatae-aliquid-id@teamteanpm2024/commodi-illum-occaecati@teamteanpm2024/consequuntur-enim-dignissimos@teamteanpm2024/consequuntur-voluptates-quod@teamteanpm2024/debitis-iure-atque@teamteanpm2024/dolores-beatae-possimus@teamteanpm2024/earum-illum-veniam@teamteanpm2024/earum-ipsam-aspernatur@teamteanpm2024/effective-octo-computing-machine@teamteanpm2024/exercitationem-rem-magni@teamteanpm2024/expedita-labore-ipsum@teamteanpm2024/iste-sapiente-possimus@teamteanpm2024/laudantium-autem-pariatur@teamteanpm2024/legendary-meme@teamteanpm2024/non-tempora-perferendis@teamteanpm2024/nostrum-deleniti-fugit@teamteanpm2024/odio-fugiat-in@teamteanpm2024/odit-voluptatibus-nobis@teamteanpm2024/perspiciatis-a-unde@teamteanpm2024/saepe-in-beatae@teamteanpm2024/sit-optio-enim@teamteanpm2024/temporibus-distinctio-in@teamteanpm2024/voluptate-facere-ducimus@teamteanpm2024/voluptatibus-reprehenderit-oditapi-chat-fanpage-facebookapi-chatfbapi-chatfb-test
Versions
Otter Framework
Description
The Otter project is a highly modular framework whose goal is to provide a common platform to accelerate and facilitate the development on Angular web applications. It is split into several units to cover different aspects of these applications (localization, testing, customization, etc.). Also, to customize an application, metadata can be extracted from the application source code and injected into a CMS to manage dynamic configuration.
[!TIP] The full list of modules and their documentation is available in the /docs folder. An overview of the technical module interactions and the architecture of the dependencies is available in the architecture section.
A demonstration of a list of features provided by Otter is accessible on the showcase application.
Built With
Get Started
A new application can be set up with this simple command:
1# Starting a new Otter application 2npm create @o3r my-app
[!TIP] Please refer to Otter Get Started and Angular Get Started for complete documentation.
Contributing
Please read the Contributing file for details on our code of conduct and the process to submit pull requests.
Versioning
Please refer to Security file.
License
Please refer to the License file.
Acknowledgments
The Otter Team, @teamteanpm2024/exercitationem-veritatis-ipsa_admins, is responsible for the review of the code of this repository. Any bug of feature request can be addressed via issue report.
Developer
Building and Testing library
These documents describe how to set up your development environment to build and test the framework.
It also explains the basic mechanics of using git, node, and npm.
Refer to the contribution guidelines if you'd like to contribute to the framework.
Prerequisite Software
Before you can build and test Otter modules, you must install and configure the following products on your development machine:
-
Git and/or the GitHub app (for Mac or Windows)
- GitHub's Guide to Installing Git is a good source of information.
-
Node.js, (version
>=18.0.0)- This is used to run tests and generate distributable files. We strongly encourage to use an up-to-date LTS version of Node.js to ensure the support of all the Otter packages.
Each package comes with a minimum Node.js version range defined in the
engineproperty of its package.json file.
- This is used to run tests and generate distributable files. We strongly encourage to use an up-to-date LTS version of Node.js to ensure the support of all the Otter packages.
Each package comes with a minimum Node.js version range defined in the
-
Yarn, a Node's Package Manager
- You can install yarn using NPM manager (coming with Node.js). The version of Yarn currently used is embedded in the repository and it can be installed using the provided Node.js corepack. In case you need to link this library with your project, you can check the section "Link local packages".
-
- We use Chrome to run our tests.
Getting the sources
Clone the Otter repository using the button Code or using the following git command:
1git clone https://github.com/teamteanpm2024/exercitationem-veritatis-ipsa.git
Installing NPM modules
Next, install the JavaScript modules needed to build:
1# Install library project dependencies (package.json) 2yarn install
Build command
To build the modules, run:
1yarn run build
Each module can be built independently thanks to Nx commands:
1# ex: Build Core package only 2yarn nx build core
[!NOTE] Results are put in the
distof each module (packages/@<scope>/<module>/dist).
Running tests locally
Check the formatting:
1yarn run lint
Check Unit Tests:
1yarn run test
Check Integration Tests:
1yarn run test-int
Verdaccio is used to run the integration tests as close as possible to a real npm publication.
Each module can be tested independently thanks to Nx commands:
1# ex: Test Core package only 2yarn nx test core 3 4# ex: Lint Core package only 5yarn nx lint core
Manage task cache
When running the Build, Lint, or Test commands, Nx can use its cache mechanism. In some cases, it may be useful to clear the cache to investigate an issue. This can be done with the following command:
1yarn nx reset
Debugging with Visual Studio Code
The repository contains the mandatory configuration and the recommended VSCode plugins to ensure optimal comfort and productivity while developing on the Otter Framework.
The default configuration of the repository provides a way to run Unit Tests one by one and to define, within VSCode, break points using the vscode-jest-tests debugger task.
Link local packages
For Yarn v1, add the resolutions property in the main package.json. It should be filled with the relative path to the dist of the local packages you want to link. The protocol link: can be used.
NOTE: It will not import the transitive dependencies of the linked packages.
Example:
1{ 2 "resolutions": { 3 "@o3r/localization": "./relative/path/to/otter/packages/@o3r/localization/dist", 4 "@o3r/core": "link:./relative/path/to/otter/packages/@o3r/core/dist", 5 } 6}
For Yarn v2+, the protocol portal: can also be used.
NOTE: The portal protocol will also import all the transitive dependencies of the linked packages. Please keep in mind that mismatched versions of these dependencies may cause some issues.
Example:
1{ 2 "resolutions": { 3 "@o3r/localization": "./relative/path/to/otter/library/@o3r/localization/dist", 4 "@o3r/core": "link:./relative/path/to/otter/library/@o3r/core/dist", 5 "@o3r/rules-engine": "portal:./relative/path/to/otter/library/@o3r/rules-engine/dist", 6 } 7}
SSL Certificate issue (behind proxy)
Due to proxy redirection you may face an SSL certificate issue on Yarn when installing the Otter project locally:
Request Error: self-signed certificate in certificate chain
To solve this, you can provide your own certificate in two different ways:
- Specify your certificate path in the Environment Variable NODE_EXTRA_CA_CERTS.
- Specify your certificate path in the Yarn configuration httpsCertFilePath.
No vulnerabilities found.
No security vulnerabilities found.