@polymer/font-roboto
Advanced tools
font-roboto loads the Roboto family of fonts from Google Fonts.
See: Documentation.
npm install --save @polymer/font-roboto
<html>
<head>
<script type="module">
import '@polymer/font-roboto/roboto.js';
</script>
</head>
<style>
body {
font-family: Roboto;
}
</style>
<body>
<p>This text is in Roboto.</p>
</body>
</html>
import {PolymerElement, html} from '@polymer/polymer';
import '@polymer/font-roboto/roboto.js';
class SampleElement extends PolymerElement {
static get template() {
return html`
<style>
p {
font-family: Roboto;
}
</style>
<p>This text is in Roboto.</p>
`;
}
}
customElements.define('sample-element', SampleElement);
If you want to send a PR to this element, here are the instructions for running the tests and demo locally:
git clone https://github.com/PolymerElements/font-roboto
cd font-roboto
npm install
npm install -g polymer-cli
polymer serve --npm
open http://127.0.0.1:<port>/demo/
polymer test --npm
FAQs
An HTML import for Roboto
The npm package @polymer/font-roboto receives a total of 19,936 weekly downloads. As such, @polymer/font-roboto popularity was classified as popular.
We found that @polymer/font-roboto demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 11 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
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.