
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
@reuters-graphics/graphics-svelte-components
Advanced tools

Svelte components for graphics pages.
Built with:
yarn add @reuters-graphics/graphics-svelte-components
<script>
import { Nav } from '@reuters-graphics/graphics-svelte-components';
</script>
<Nav />
... for details on using all the components included.
If you're using this package with SvelteKit (which uses Vite), you'll likely need to add some of its dependencies to Vite's dependency pre-bundling config. For example:
export default {
// ...
kit: {
// ...
vite: {
// ...
optimizeDeps: {
include: ['lodash-es', 'pym.js', 'classnames', 'ua-parser-js'],
},
},
},
};
If you're using the graphics kit this config is already included.
First step: make a branch for your new component.
Next, add your component in a folder one level below src/lib
, for example:
src/
lib/
MyComponent/ 👈
index.svelte 👈
Be sure to export your component from the library's entry module, src/lib/index.js
:
// src/lib/index.js
export { default as MyComponent } from './MyComponent/index.svelte';
To document and demo your component, add a docs.svx
file in your component directory:
MyComponent/
docs.svx 👈
index.svelte
Use Svelte in Markdown syntax to demo your component and document its features.
Note, you must add some basic frontmatter data -- a title, description and slug -- to make your demo page discoverable in the demo site.
---
title: MyComponent
description: A component that does things.
slug: my-component
---
<script>
import MyComponent from './index.svelte';
import DemoContainer from '../_docs/DemoContainer/index.svelte';
</script>
# MyComponent
A component that does things.
```svelte
<script>
import { MyComponent } from '@reuters-graphics/graphics-svelte-components';
</script>
<MyComponent />
```
<DemoContainer>
<MyComponent />
</DemoContainer>
When you're ready, make a pull pequest for your component.
Once you've completed documenting your component, commit it and then version the package, which will publish the library to npm:
git add .
git commit -m "my new component added"
git push origin master
npm version patch
FAQs

The npm package @reuters-graphics/graphics-svelte-components receives a total of 15 weekly downloads. As such, @reuters-graphics/graphics-svelte-components popularity was classified as not popular.
We found that @reuters-graphics/graphics-svelte-components demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.