JGit JGit is an (new-style BSD) licensed, lightweight, pure Java library implementing the: • repository access routines • network protocols • core version control algorithms Users JGit has very few dependencies, making it suitable for embedding in any Java application, whether or not the application is taking advantage of other Eclipse or OSGi technologies. JGit can be found within: •, Git integration for Eclipse •, a web based peer review system for Git •, Git Support for NetBeans •, Git server for managing, viewing, and serving Git repositories •.

And some commercial products.

This is the API documentation for the Vault KV secrets engine.

Generator to create a standalone library in seconds. If you want to create an Angular library with directives, services and/or pipes, then this generator is just what you need.

This generator aligns with the and automatically generates a, a UMD bundle, a single metadata.json and type definitions to make your library ready for AOT compilation by the consuming Angular application. Watch to learn more about the Angular Package Format. $ npm run build This will generate a dist directory with: • a package.json file specifically for distribution with Angular listed in the peerDependencies • sample-library.js: a Flat ES Module (FESM) file that contains all your library code in a single file • sample-library.umd.js: a Universal Module Definition (UMD) bundle file that contains all your library code in UMD format for use in Node.js, SystemJS or via a script tag (e.g. In Plunker, Fiddle, etc) • *.d.ts: type definitions for you library • sample-library.metadata.json: metadata for your library to support AOT compilation Generating documentation for your library From the root of your library directory, run. $ npm run playground Changes to your library code will be updated live in the browser window: Consuming your library in a local application during development To consume your library in a local application before you publish it to npm, you can follow the following steps: • Create your library: $ yo angular2-library Let's assume you name your library sample-library. • Navigate to the sample-library directory: $ cd sample-library • Compile your library files: $ npm run build • From the sample-library/dist directory, create a symlink in the global node_modules directory to the dist directory of your library: $ cd dist $ npm link • Create a new Angular app.

Let's assume you use angular-cli: $ cd /your-projects-path $ ng new my-app • Navigate to the my-app directory: $ cd my-app • From the my-app directory, link the global sample-library directory to node_modules of the my-app directory: $ npm link sample-library • Import SampleModule in your Angular application. 'flatModuleId ': '@scope/library-name ' See for more information.

How can I avoid recompilation during development If you experience issues () or want to avoid constant recompilation of your library during development, you can also npm link src instead of npm link dist in step 4 of the process above. This will let you consume the TypeScript code directly from the src directory of your library instead of the generated bundle from the dist directory. This increases development speed if you are testing your library in a local Angular application, but remember to test the generated bundle using npm link dist after you finish writing your code, to ensure that your generated bundle is working as expected before you publish your library to NPM. How can I use.scss files? Simply store your styles in a file with a filename extension of scss and reference it in your component's styleUrls property. So if you have a sample.component.scss.