Gathering detailed insights and metrics for @auroratide/svelte-custom-element-transitions
Gathering detailed insights and metrics for @auroratide/svelte-custom-element-transitions
npm install @auroratide/svelte-custom-element-transitions
Typescript
Module System
Node Version
NPM Version
69.6
Supply Chain
74.7
Quality
75.1
Maintenance
50
Vulnerability
100
License
TypeScript (100%)
Total Downloads
3,631
Last Day
1
Last Week
11
Last Month
104
Last Year
724
2 Stars
36 Commits
2 Watching
1 Branches
1 Contributors
Minified
Minified + Gzipped
Latest Version
0.1.1
Package Id
@auroratide/svelte-custom-element-transitions@0.1.1
Unpacked Size
11.22 kB
Size
3.72 kB
File Count
7
NPM Version
7.10.0
Node Version
16.0.0
Cumulative downloads
Total Downloads
Last day
-87.5%
1
Compared to previous day
Last week
-81%
11
Compared to previous week
Last month
23.8%
104
Compared to previous month
Last year
-49%
724
Compared to previous year
It's a known issue that Svelte transitions do not work when compiling to custom elements (aka, web components). There's an active Pull Request which has been around for several months.
Hopefully that PR will be merged in the near future. But in case it doesn't, at least you have @auroratide/svelte-custom-element-transitions! This tiny module works around the issue by applying the CSS rules directly to the target node with Javascript.
1<script> 2 import { fade } from '@auroratide/svelte-custom-element-transitions' 3</script> 4 5<h1 transition:fade>Hello!</h1>
This module also provides a higher order function which can make custom transitions work as well.
1import { forCustomElement } from '@auroratide/svelte-custom-element-transitions' 2 3export const myTransition = forCustomElement((node, params) => { 4 // ... 5})
See the examples for different possible use cases.
By the way, each example is run as an automated test!
This library is intended to become deprecated as soon as Svelte has an official solution. In the meantime, here are some helpful notes for anyone who wants to contribute:
npm run build
: Build the librarynpm test
: Run verification script (in Chrome)npm run example
: See transitions in actionNo vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
no SAST tool detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
27 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-01-27
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More