JSPM

@progress/telerik-angular-report-viewer

1.17.503
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 3276
  • Score
    100M100P100Q140976F
  • License http://www.telerik.com/purchase/license-agreement/reporting-dlw-s

Progress® Telerik® Report Viewer for Angular (PREVIEW)

Package Exports

  • @progress/telerik-angular-report-viewer

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@progress/telerik-angular-report-viewer) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

###Progress® Telerik® Report Viewer for Angular component

Structure

  • The src directory contains the component source code. All files should have the .ts extensions so that the build scripts may pick them.

  • The src/main.ts file should import and re-export all public components of the package. It is used for the build-cdn task. It is also the main entry point for the NPM package (as specified by the package.json). The build-npm-package transpiles it to dist/npm/js/main.js;

  • The src/telerik-report-viewer.component.ts file is the actual sample component implementation.

  • The src/util.ts is an optional example of an additional file - you may remove it if unnecessary.

  • The examples directory hosts the demos for the component. As a bare minimum, the component should have a basic usage and a CDN example. The CDN example should work as expected after the build-cdn task has been run.

  • The test directory contains the component tests. They are transpiled just like the source code itself, and run with Jasmine in Karma (PhantomJS).

  • The e2e directory contains the end-to-end tests. They are transpiled and run with Jasmine in Karma (Google Chrome).

  • The docs directory contains markdown files that document the specifics of the component.