Foundation for Emails, currently at stable version 2.5.1, is a robust open-source framework designed for building responsive HTML emails that render consistently across various email clients, including challenging ones like Outlook. Originally known as Ink, it transitioned to a Sass-based codebase with its 2.0.0 release, incorporating the Inky templating language, which simplifies email layout by converting custom HTML tags into complex, client-compatible table structures. While releases were infrequent for several years, recent activity (v2.3.0, v2.4.0, v2.5.0, v2.5.1 between 2022-2024) indicates a more active maintenance phase. Its key differentiators include comprehensive testing across email clients, the Inky templating system, and support for both Node.js-based build workflows (via a template stack) and integration into Ruby on Rails projects via a dedicated gem.
npm install foundation-emailsNo compatibility data collected yet for this library.
Sets up a new Foundation for Emails project using the official template, demonstrating the core `npm install`, `npm start`, and `npm run build` commands for local development and production compilation.
Refer to the official Migration Guide for upgrading from Ink 1.0 to Foundation for Emails 2.0.
Ensure your Gulp build system uses `gulp-sass` v5 or newer with Dart Sass. Update `node-sass` related dependencies in your `package.json` to be compatible or remove them if migrating fully to Dart Sass. Check `gulpfile.babel.js` in the `foundation-emails-template` for updated configurations.
Use Node Version Manager (nvm) to install and switch to Node.js v10.x. For example: `nvm install 10 && nvm use 10`. More recent versions (2.5.0+) may have improved Node compatibility, but testing with v10 is safest if issues arise.
While `foundation-emails` remains functional, consider monitoring the `Inky` project for future directions and new feature development. Existing projects will likely continue to receive maintenance updates.
Avoid relying on JavaScript for critical functionality or interactive elements within your email designs. Focus on CSS and HTML for responsive layouts. Any included JS is for enhancements where supported, not core functionality.
Update `gulp-sass` to a version compatible with Dart Sass (e.g., `gulp-sass@5.0.0` or newer), and ensure `sass` (Dart Sass) is installed as a dependency instead of `node-sass`. You may need to remove `node-sass` from `package.json` and reinstall dependencies.
Verify you are using a compatible Node.js version (historically Node.js v10.x was recommended for the template). Update global `foundation-cli` and `gulp` (`npm install -g foundation-cli gulp`). If problems persist, try deleting `node_modules`, `package-lock.json`, and reinstalling `npm install`.
Foundation for Emails' JavaScript components are typically bundled for client-side inclusion, not designed for direct Node.js ESM/CJS module import. Ensure your build pipeline correctly handles module compilation if you're attempting to customize Foundation's JS. If you're importing external modules, ensure your project supports ESM (e.g., by setting `"type": "module"` in `package.json` or using a transpiler like Babel).
No dependency data recorded yet.