Menu icon Foundation
Sites: npm run build breaking dropdown and sticky menu

Hey all,

I see this issue addressed on github but I am still not 100% sure what the fix for this issue is. From what I understand it is a problem with unCSS stripping dynamic classes out of the css because they are not there when the build process runs. Both work perfectly when running browsersync with the src folder, but break in dist.

Here are a couple threads talking about it: 
https://github.com/zurb/foundation-sites/issues/7435
https://github.com/zurb/foundation-sites/issues/7909

If anyone here could point me to a fix it would be much appreciated!

npm buildsitesdropdownmenusticky

Hey all,

I see this issue addressed on github but I am still not 100% sure what the fix for this issue is. From what I understand it is a problem with unCSS stripping dynamic classes out of the css because they are not there when the build process runs. Both work perfectly when running browsersync with the src folder, but break in dist.

Here are a couple threads talking about it: 
https://github.com/zurb/foundation-sites/issues/7435
https://github.com/zurb/foundation-sites/issues/7909

If anyone here could point me to a fix it would be much appreciated!

Rafi Benkual over 3 years ago

Correct - you can remove the UnCSS pipe in the gulpfile or add the missing classes to the ignore file. There is some work being done that can be contributed towards to auditing all the state classes and adding them to the UnCSS ignore. In the meantime, removing it from the gulpfile works.