Reduce unused javascript from assets.auth.magic.link
See original GitHub issue✅ Prerequisites
- Did you perform a cursory search of open issues? Is this question already asked elsewhere?
- Are you reporting to the correct repository (
magic-sdk
)?
❓ Question
assets.auth.magic.link is taking majority of resources. is there a way to reduce unused bytes ?
🌎 Environment
Software | Version(s) |
---|---|
magic-sdk |
8.1.1 |
Browser | Google Chrome |
yarn |
1.22.19 |
Operating System | Mac OS Monterey 12.4 (21F79) |
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Issues · magiclabs/magic-js - GitHub
Magic browser/React Native JavaScript SDK is your entry-point to integrating ... Reduce unused javascript from assets.auth.magic.link ❓ Question.
Read more >Magic for Web - Magic Link
The Magic SDK for client-side JavaScript is your entry-point to secure, passwordless authentication for your web-based app. This guide will cover some ...
Read more >How to Remove (or Reduce) Unused JavaScript on WordPress
On the other hand, unloading unnecessary assets will reduce the size of JS on the page. It's technically reducing unused JS rather than...
Read more >"remove unused css/r/r" - Isotropic
Asset Clean Up Pro A plugin that allows us to remove unused CSS and JavaScript from ... have a lot of tutorials linked...
Read more >Supabase Documentation
You can install @supabase/supabase-js via CDN links. <script src="https://cdn.jsdelivr.net/npm/@supabase ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kesar We support a plethora of blockchains and use code splitting to only deliver what is needed based on the SDK use case. Unfortunately, most blockchain libraries are not optimized for bundle size. Our authentication relies on Ethereum libraries for creating the DID tokens. There is some work that can be done to reduce the overall bundle size however the biggest offenders won’t be trivial.
I do think the lack of Cache TTL can be addressed in the interim.
Thank you for bringing this up Kesar. We’ll be discussing this internally and I’ll respond once we have an update.