🐛 Library doesn't work clientside
See original GitHub issueThanks for the amazing work.
I noticed that the library doesn’t work on any browser. It results in the error:
Refused to set unsafe header "user-agent"
Access to XMLHttpRequest at 'https://github.com/a-tokyo' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Your schema is amazing and i’d love to use this, however I will have to use https://github.com/itaditya/simple-unfurl for now as it works clientside as well
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Adding Client-side library doesn't work in Visual Studio 2019 ...
This documentation says an autocomplete of available client-side javascript libraries will be displayed. But it doesn't work. So its not possible to see ......
Read more >"Manage Client-Side Libraries" menu not appearing
Open Microsoft.Web.LibraryManager.vsix to launch the Visual Studio Installer. Then you will have the Add->Client Side Library in your Context ...
Read more >Library Manager: Client-side content manager for web apps
Library Manager (“LibMan” for short) is Visual Studio's experimental client-side library acquisition tool. It provides a lightweight, ...
Read more >Client-side javascript: How to include third party frameworks?
I'm wondering how to embed these frameworks in my app. Short answer: Use aliases? If it can be automated, I don't see any...
Read more >Chapter 13 JavaScript Libraries - Client-Side Web Development
Chapter 13 JavaScript Libraries. Many web programmers encounter the same programming requirements as they develop interactive web sites.
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 Free
Top 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
Yes I get it 😕 so I added the proxy CORS thing to avoid these issues.
However I think I will just add a backend endpoint today that handles this. I am just worried the library would have the same errors in the backend as well @jacktuck
You shouldn’t have the same issue as you’d have control of the endpoint - meaning you can add CORS response headers - either wildcard or specific to your domain(s).