foundation / foundation/yeti

Pointing Custom download of Foundation to a CDN

Open
#15,532 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
29.8k
Forks
5.4k
Avg merge
25m
Merged PRs (30d)
1

Description

We use a custom package of v6.5.1 of Foundation (for some reason the later versions did not work on our website).

Having used it for a couple of years, we decided to use a CDN to host our static javascript and css files. Unfortunately, when we point the to the CDN, we get errors along the lines of "foundation __webpack_require__ is not defined"

Has anyone migrated a custom package of Foundation to a CDN?

Not sure what we need to change.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported Foundation v6.5.1 custom-package setup with its JavaScript and CSS loaded from a CDN, focusing on the “foundation __webpack_require__ is not defined” error. Determine the required CDN loading or packaging arrangement and verify that the custom Foundation assets load without that error on the website.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.