@openmrs/angularjs-openmrs-api
Advanced tools
JavaScript AngularJS (1.x) library exposing OpenMRS API
npm install @openmrs/angularjs-openmrs-api --save
ES6: import openmrsApi from '@openmrs/angularjs-openmrs-api';
ES5: var openmrsApi = require('@openmrs/angularjs-openmrs-api');
You need to have Node 6.x installed. We recommend using nvm or nvm-windows to install Node.
Installing dependencies: npm install (once after code checkout or when dependencies change)
Development build: npm run build:dev
Clean build: npm run clean && npm run build:dev
Running tests continously: npm run test:dev
Production build: npm run build
Release: npm version 1.0.0 && git push upstream master && git push upstream --tags
Linking is a feature of npm, which allows you to modify the library and test modifications in your project.
npm link and npm run build from the lib directory.npm link @openmrs/angularjs-openmrs-api from your project directory.In order to unlink do:
npm unlink @openmrs/angularjs-openmrs-api and npm install from your project directory.FAQs
AngularJS (1.x) library for OpenMRS API
We found that @openmrs/angularjs-openmrs-api demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.