oe-chart
Advanced tools
Readme
A template element , used to create oe-ui Polymer 3 elements
First, make sure you have the Polymer CLI and npm (packaged with Node.js) installed. Run npm install to install your element's dependencies, then run polymer serve to serve your element locally.
The below command generates a JSON file that polymer reads to create documentation. This JSON is created based on the JSDoc comments present in the file provided.
$polymer analyze oe-chart.js > analysis.json
Once analysis.json is created run the below command to serve the file. Optional parameter --open to launch browser.
$ polymer serve [--open]
Once the files are served using polymer serve navigating to \test runs the test files
Your application is already set up to be tested via web-component-tester. Run polymer test to run your application's test suite locally.
FAQs
A template element , used to create oe-ui Polymer 3 elements
The npm package oe-chart receives a total of 0 weekly downloads. As such, oe-chart popularity was classified as not popular.
We found that oe-chart 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
This episode of the Risky Biz podcast discusses how the rise of small open source packages and the shift towards individual maintainers makes the ecosystem more vulnerable to supply chain attacks.
Product
Streamline your login process and enhance security by enabling Single Sign-On (SSO) on the Socket platform, now available for all customers on the Enterprise plan, supporting 20+ identity providers.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.