doiuse

library6.0.6jsnpmunverified

Doiuse is a JavaScript library and CLI tool that lints CSS code for browser support issues by comparing features used in the CSS against the Can I use database. It helps developers identify CSS properties and values that are not supported by their target browser list, preventing unexpected rendering problems. The current stable version is 6.0.6, released in early 2024, with maintenance releases occurring as needed to fix bugs and update feature definitions. It integrates well into build pipelines, notably as a PostCSS plugin or a transform stream. A key differentiator is its direct reliance on the `caniuse` database for accurate, up-to-date compatibility data, allowing for highly customizable browser targets using `browserslist` syntax. While it focuses on identifying unsupported features, its "naive" detection approach means it primarily checks for direct property/value matches rather than complex runtime interpretation, offering a fast and focused linting experience.

testing http-networking

npm install doiuse

github ↗package ↗

INSTALL

IMPORT

SIG · DOIUSE

doiuse

testingjavascriptv6.0.6

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.

DoIUse

✓ import DoIUse from 'doiuse/lib/DoIUse.js';

✗ import { DoIUse } from 'doiuse';

The primary PostCSS plugin class is a default export from its specific path, not a named export from the main package. This is due to its internal structure.

doiuse

✓ import doiuse from 'doiuse/stream';

✗ import { doiuse } from 'doiuse';

When using doiuse as a transform stream, the function is a default export from the 'doiuse/stream' entry point. The main 'doiuse' package itself primarily exposes the CLI.

require('doiuse')

✓ const doiuseCli = require('doiuse');

✗ const { DoIUse } = require('doiuse');

The main 'doiuse' export is primarily for the CLI. For programmatic use, prefer `doiuse/lib/DoIUse.js` for PostCSS or `doiuse/stream` for stream-based processing, especially since v6.x for better ESM compatibility.

DoIUse (CommonJS)

✓ const DoIUse = require('doiuse/lib/DoIUse');

✗ const DoIUse = require('doiuse');

For CommonJS environments, the PostCSS plugin class is found at `doiuse/lib/DoIUse`. Note the missing `.js` extension for CommonJS imports often works, but explicit is better for clarity.

This quickstart demonstrates how to use `doiuse` as a PostCSS plugin to lint CSS for browser compatibility, targeting specific browser versions and logging unsupported feature usages to the console.

import postcss from 'postcss'; import DoIUse from 'doiuse/lib/DoIUse.js'; const cssInput = ` a { background-size: cover; display: flex; /* flexbox support */ user-select: none; scroll-snap-align: start; } .gradient { background-image: conic-gradient(white, black); } `; postcss(new DoIUse({ browsers: ['last 2 chrome versions', 'ie 11'], // Target specific browsers ignore: ['flexbox', 'user-select-none'], // Optional: ignore specific features by 'caniuse' ID ignoreFiles: ['**/node_modules/**'], // Optional: ignore files matching these globs onFeatureUsage: (usageInfo) => { // Log detailed information about each unsupported feature found console.log(`[doiuse] ${usageInfo.message} in ${usageInfo.feature} for ${usageInfo.browsers.join(', ')} at ${usageInfo.source.start.line}:${usageInfo.source.start.column}`); } })).process(cssInput, { from: 'example.css' }) .then(result => { console.log('\nProcessed CSS (no changes made by doiuse):\n', result.css); }) .catch(error => { console.error('PostCSS processing failed:', error); });

doiuse --version

Debug

Known issues

breakingVersion 6.0.0 of `doiuse` dropped support for Node.js v12 and v14. Projects must upgrade to Node.js v16 or higher.

fix

Upgrade your Node.js environment to version 16 or newer. For projects that cannot upgrade Node.js, remain on `doiuse` v5.x or earlier.

affects: >=6.0.0

breakingOlder versions of `doiuse` (prior to v4.3.0) dropped support for Node.js versions older than 10.x and 4.x respectively. Ensure your Node.js version meets the minimum requirements for your `doiuse` version.

fix

Check the `engines` field in `package.json` for the specific `doiuse` version you are using. Upgrade Node.js or `doiuse` as necessary.

affects: <4.3.0

gotchaThe `doiuse` package uses specific import paths for its PostCSS plugin and stream API (e.g., `doiuse/lib/DoIUse.js`, `doiuse/stream`). Direct `import DoIUse from 'doiuse'` or `require('doiuse')` will not work for programmatic usage as intended for the plugin or stream.

fix

For the PostCSS plugin, use `import DoIUse from 'doiuse/lib/DoIUse.js'` (ESM) or `const DoIUse = require('doiuse/lib/DoIUse');` (CJS). For the stream, use `import doiuse from 'doiuse/stream'` or `const doiuse = require('doiuse/stream');`.

affects: >=4.0.0

gotchaThe feature detection in `doiuse` is described as 'quite naive,' primarily relying on regex/substring matches of property and value names. It may not catch all nuanced browser compatibility issues, especially those involving complex CSS interactions or JavaScript polyfills.

fix

Treat `doiuse` as a strong first line of defense for basic property/value support. Supplement its findings with actual browser testing and more advanced linting tools if detailed interaction compatibility is critical. Manually inspect the `data/features.js` file for specifics on how features are detected.

affects: >=4.0.0

Errors

Common errors & fixes

Error: Cannot find module 'doiuse/lib/DoIUse.js'

Attempting to import the `DoIUse` class incorrectly, often from the main package entry point or with a wrong path.

fix

Ensure you are importing from the correct path: `import DoIUse from 'doiuse/lib/DoIUse.js';` for ESM or `const DoIUse = require('doiuse/lib/DoIUse');` for CommonJS.

SyntaxError: Unexpected token 'export' (for ESM usage in CJS context) OR require() of ES Module (for CJS usage in ESM context)

Mixing ESM `import` statements with CommonJS `require()` or vice-versa, or running a module type in an incompatible environment.

fix

For ESM, ensure your project is configured with `"type": "module"` in `package.json` and use `import` statements. For CommonJS, use `require()` and ensure files are `.js` or `.cjs`. Doiuse v6.x is largely ESM-first, so adjust your imports accordingly.

TypeError: doiuse is not a function

This typically happens when trying to call `doiuse` directly after a `require('doiuse')` which returns the CLI function, not the PostCSS plugin or stream constructor.

fix

For programmatic use, ensure you are importing the specific PostCSS plugin or stream entry point: `const doiusePlugin = require('doiuse/lib/DoIUse');` or `const doiuseStream = require('doiuse/stream');`.

Upgrade

Version history

6.0.6latest on npm

Audit

Dependencies

postcssrequiredRequired when using doiuse as a PostCSS plugin, which is a common integration pattern for CSS processing pipelines.

Agent activity

7 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/anandthakker/doiuse ↗

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