@angular.studio/authentication-service
Advanced tools
This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.2.9.
This library was generated with Angular CLI version 11.2.9.
Run ng generate component component-name --project angularstudio-authentication to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project angularstudio-authentication.
Note: Don't forget to add
--project angularstudio-authenticationor else it will be added to the default project in yourangular.jsonfile.
Run ng build angularstudio-authentication to build the project. The build artifacts will be stored in the dist/ directory.
After building your library with ng build angularstudio-authentication, go to the dist folder cd dist/angularstudio-authentication and run npm publish.
Run ng test angularstudio-authentication to execute the unit tests via Karma.
To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.
FAQs
This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.2.9.
We found that @angular.studio/authentication-service demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
