localhost cors block when using pro

[GedMarc]

Describe the bug

For a pro website being developed

Access to script at 'https://ka-p.webawesome.com/webawesome/components/tab-panel/tab-panel.js' from origin 'http://localhost:4200' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

To Reproduce

Steps to reproduce the behavior:

1. Create an angular application as per docs
2. ng serve
3. Visit localhost 4200 - CORS

[GedMarc]

@claviska Hey, please can I get some help? The CDN for pro when using WA Pro + FA Pro gives cors errors :(

When deploying (domain is added in FA) - https://jwebswing.com

Access to script at 'https://ka-p.webawesome.com/webawesome/components/tab/tab.js' from origin 'https://jwebswing.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Are the PRO WA Kits ready for adoption?

[claviska]

When deploying (domain is added in FA)

To be clear, are you adding the domain in Font Awesome's dashboard or in Web Awesome's dashboard? You'll need to add the public domain to Web Awesome's dashboard.

As for localhost, it looks like you're referencing a pro kit URL without the kit code:

https://ka-p.webawesome.com/webawesome/components/tab/tab.js

Are you importing this component directly, or are you using a hosted project? e.g. one that gets imported like this:

https://kit.webawesome.com/15db5478c9f145fe.js

If you're importing it directly, the Pro CDN URL should include your kit code:

https://ka-p.webawesome.com/kit/e6907f424ffd4ea7/webawesome@3.3.1/webawesome.loader.js

The latter isn't currently documented, but it works and we'll be switching over to this as one of the recommended ways to consume Web Awesome in the near future.

Thanks for clarifying!

[MarcMagonMNS]

This was caused by having dual-initialization options - when working local forcing the data-webawesome directory to / so we could avoid the localhost CORS and work, and having the web-awesome kit defined which is the proper way.

I see (with no changes on our end) that the localhost no longer throws CORS - THANKS FOR THE QUICK RESOLUTION!

When removing the local data directory, it now routes properly.