scow

library4.0.0-alpha.5jsnpmunverified

Scow is an HTML email inliner and bundler designed to prepare modern HTML and CSS for consistent rendering across a diverse range of email clients. Historically, email clients exhibit inconsistent support for external stylesheets and `<style>` tags within the `<head>` of an HTML document, often stripping them entirely. This necessitates that CSS be applied directly as `style` attributes on individual HTML elements for reliable presentation. Scow automates this critical inlining process, abstracting away the complexities of email client rendering quirks. Additionally, it aims to bundle associated assets like images, potentially converting them to data URIs. Currently available as `4.0.0-alpha.5`, the package is undergoing active alpha development, meaning its API and feature set are subject to change without strict adherence to semantic versioning until a stable release. Its core value lies in streamlining the email development workflow, ensuring that visually rich emails display as intended, despite the varied and often outdated rendering engines used by different email services and applications.

communication

npm install scow

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · SCOW

scow

communicationjavascriptv4.0.0-alpha.5

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

inline

✓ import { inline } from 'scow';

✗ const scow = require('scow'); const inlinedHtml = scow.inline(...);

The primary `inline` function for processing HTML is typically a named export. While CJS `require` might work in some contexts, modern Node.js and bundler setups prefer ESM `import`.

ScowConfig

✓ import type { ScowConfig } from 'scow';

For TypeScript users, import the configuration interface to ensure type safety when defining options.

bundleAssets

✓ import { bundleAssets } from 'scow';

This function is expected to handle asset bundling (e.g., converting images to data URIs or local paths) and might be a separate utility within the library.

This quickstart demonstrates how to use `scow` to inline CSS styles from a `<style>` block in an HTML email template directly into the HTML elements' `style` attributes, preparing it for various email clients. It also shows basic error handling.

import { inline } from 'scow'; import { readFileSync } from 'node:fs'; import { join } from 'node:path'; async function processEmailTemplate() { const templatePath = join(process.cwd(), 'email-template.html'); const htmlContent = readFileSync(templatePath, 'utf-8'); // Assume email-template.html looks something like: // <html><head><style>h1 { color: #1a73e8; }</style></head><body><h1>Hello, World!</h1></body></html> try { const inlinedHtml = await inline(htmlContent, { // Optional configuration, e.g., to keep original style tags for media queries // keepOriginalStyleTags: true, // Optional: Specify base URL for resolving relative paths if bundling external assets // baseUrl: 'https://example.com/assets/', }); console.log('Successfully inlined HTML:\n', inlinedHtml); } catch (error) { console.error('Error inlining email:', error); } } processEmailTemplate(); // To make this runnable, create a file named 'email-template.html' in the same directory: //  // <!DOCTYPE html> // <html> // <head> // <meta charset="utf-8"> // <title>Styled Email</title> // <style type="text/css"> // body { font-family: sans-serif; margin: 0; padding: 20px; background-color: #f6f6f6; } // .container { max-width: 600px; margin: 0 auto; background-color: #ffffff; padding: 20px; border-radius: 8px; box-shadow: 0 4px 8px rgba(0,0,0,0.1); } // h1 { color: #333333; font-size: 24px; margin-bottom: 15px; } // p { color: #555555; font-size: 16px; line-height: 1.5; } // .button { display: inline-block; padding: 10px 20px; margin-top: 20px; background-color: #1a73e8; color: #ffffff; text-decoration: none; border-radius: 5px; } // @media only screen and (max-width: 620px) { // .container { width: 100% !important; border-radius: 0; } // body { padding: 0; } // } // </style> // </head> // <body> // <div class="container"> // <h1>Welcome to Our Service!</h1> // <p>Thank you for signing up. We're excited to have you on board.</p> // <p>Explore our features and get started today.</p> // <a href="#" class="button">Get Started</a> // </div> // </body> // </html>

scow --version

Debug

Known issues

breakingScow is currently in an alpha release phase (e.g., `4.0.0-alpha.5`). This means the API is not yet stable and is subject to frequent and significant breaking changes without prior notice. Use in production with extreme caution.

fix

Always pin to an exact alpha version (e.g., `"scow": "4.0.0-alpha.5"`) and regularly check the project's GitHub repository for API updates and migration guides before upgrading.

affects: >=4.0.0-alpha.0

gotchaEmail clients vary greatly in their support for CSS properties, even when inlined. While scow handles the inlining mechanism, it does not guarantee that all CSS properties will be rendered correctly by every email client (e.g., Outlook's reliance on Word's rendering engine).

fix

Thoroughly test all inlined email templates across multiple email clients and devices (e.g., using Litmus or Email on Acid) to ensure consistent rendering. Design emails with a 'lowest common denominator' approach, favoring widely supported CSS properties.

affects: >=4.0.0-alpha.0

gotchaIncorrect handling of external stylesheets or image paths can lead to broken assets in the final email. Scow aims to bundle assets, but relative paths or unresolvable URLs will result in missing content.

fix

Ensure all external assets (images, fonts, etc.) are hosted on publicly accessible URLs. Use the `baseUrl` configuration option if your HTML template uses relative paths that need to be resolved against a specific base URL for asset bundling.

affects: >=4.0.0-alpha.0

deprecatedOlder versions of email inliners (and potentially early alpha versions of scow) might have defaulted to CommonJS `require()` syntax. As of recent Node.js versions and the general shift in the JavaScript ecosystem, ESM `import` is the preferred and often only supported module system for newer libraries.

fix

Always use `import { ... } from 'scow';` for module loading. If encountering issues in a CommonJS environment, ensure your project is configured for dual ESM/CJS support or use dynamic `import()` for ESM-only packages.

affects: <4.0.0

Upgrade

Version history

4.0.0-alpha.5latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

15 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/gakimball/scow ↗

packagehttps://www.npmjs.com/package/scow ↗

homepagehttps://scow.email ↗