Using Foundation 6 in Angular 4 (or 2)

I recently started a project that’s built using Angular 4. As a fairly longtime Angular 1 user, the transition from 1.X to 4.X was…well…big. TL;DR, Angular 4 is nothing like Angular 1, so I had to relearn just about everything about the framework (including how to use typescript which has come with its own set of challenges).

In addition, our frontend dude is a fan of Foundation, and we’re using that for all our frontend framework needs. Recently, as I was working on implementing a modal, I couldn’t get it to trigger, despite following the docs line-for-line. If you’ve had trouble getting Foundation’s JS components to work with Angular 2+, here’s how to solve the problem.

Dynamic Components and Binding

Let’s look at how you’d set up a simple modal in Foundation:

<button class="button" data-open="myModal">Add Action</button>                                                
<div class="large reveal" id="myModal" data-reveal>                                                           
  <h1>My Modal Title</h1>                                                                                            
  <p>This is the body of my modal</p>

Without getting too in the weeds with how Foundation works internally, here’s what’s happening. Defining the data-open attribute on the button binds that button’s click to the item it’s pointing at, in this case, #myModal. When Foundation loads up, it runs through and finds all of these attributes, binds listeners to them, and waits to take action when you click.

Here’s the problem. With Angular, components are injected into the DOM after Foundation has loaded. When you load up a new component, and inject it, Foundation doesn’t know it’s there. We need to tell Foundation to reinitialize and bind again, so these attributes will get wired up.

Here’s how we do it. Our super simple Angular 2+ component looks like this:

{ import Component } from '@angular/core';
declare var $:any

  selector: 'my-component',
  templateUrl: './my-component.html'
  // other stuff here

export class MyComponent implements OnInit {
  constructor() {}
  ngOnInit() {

A couple things to note. First, we declare $ as a variable in the component that we can use (note that this is a typescript thing, if you’re not using typescript, you likely won’t need this), and give it a type of any. This gives us access to jQuery, which is needed to call Foundation. Then, in our ngOnInit method on the component, we call $(document).foundation(), which tells Foundation to reinitialize and bind to the DOM again. Since our component’s HTML is now in the DOM, it finds the attributes, binds the listeners, and you’re in business!

This should work for Angular 2 and above, and for Foundation for Sites 6.X. Other versions, YMMV.

Related Posts

I Launched a New Podcast, and I Want You to Call In

I just launched a new podcast called Design By Committee, dedicated to answering your questions about UX, product design, content, strategy and anything else tech.

Shitty Sales Have Made Product Development Harder

Shitty, one-sided sales processes have made product development much more difficult for early stage startups.

Why I'm Cold Emailing You

You might have gotten a cold email from me. Tasteless? Some people think so. Here's why I'm doing it.

How I Found Your Email

I've been cold emailing a lot of people, and many folks are surprised that I found their email. Here's where I dug it up.

Announcement: The Most Exciting Thing I've Done

Today, I'm announcing the most exciting project I've been involved with. It's called CrowdSync, and it helps to automate paperwork, communication and logistics when dealing with groups of people. Read on for why this is so big.

How to Post to Private Slack Channels from Zapier

If you automate posting to Slack via Zapier, you might need to post to a private channel. It's not entirely obvious how to do it, but actually pretty damn easy.

Sharing is the Currency of the Web

You consume free content all day on the web. The best way to pay back the people creating it? Share it.

The Magic of Low Fidelity

High-fidelity documentation is great, but it has a hidden dark side. Learn to embrace low-fidelity documentation, and you'll be amazed at the benefits.

Why You Should Blog More (Data)

When you stop blogging, people stop coming. Simple enough. Here's the proof.

Using a Linter Will Make You a Better Dev

Using a linter while you write code won't only make your code better formatted, it'll make you a better programmer.