# Is @alifd/next ESM-only? Can you require() it?

> @alifd/next@1.27.34 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

A configurable component library for web built on React.

Latest version 1.27.34, published Mar 31, 2026.

@alifd/next ships CommonJS only. require("@alifd/next") should work on every Node.js version the package supports; the runtime probe has not run for this version. import "@alifd/next" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

It also declares a "module" field, so bundlers such as webpack, Vite and esbuild pick up an ESM build for tree-shaking.

## What to do

1. require("@alifd/next") should work on every Node.js version the package supports; the runtime probe has not run for this version.
2. From ES modules use the default import: import next from "@alifd/next"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 1.27.34 (Mar 31, 2026)
- Module format: CommonJS
- Last CommonJS version: 1.27.34
- TypeScript types: bundled
- Node engines: not declared
- Weekly downloads: 13K
- License: MIT

## Runtime test results for @alifd/next@1.27.34

Runtime probe pending for this version (install failed: error: ConnectionRefused downloading package manifest @alifd/next). The facts above come from package.json.

## How to import @alifd/next

ES modules:

```js
import next from "@alifd/next";
```

CommonJS:

```js
const next = require("@alifd/next");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (436 versions; the newest 60 shown).

| Versions | Format | First published |
|---|---|---|
| 1.26.13 – 1.27.34 | CommonJS | Feb 27, 2023 |

## Frequently asked

**Is @alifd/next ESM-only?**

@alifd/next@1.27.34 is a CommonJS package. @alifd/next ships CommonJS only. require("@alifd/next") should work on every Node.js version the package supports; the runtime probe has not run for this version. import "@alifd/next" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

**Can I import @alifd/next with ES module syntax?**

Yes. import next from "@alifd/next" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.

**Does @alifd/next ship TypeScript types?**

Yes. @alifd/next bundles its own type declarations; no @types package is needed.

## Links

- [@alifd/next on npm](https://www.npmjs.com/package/@alifd/next)
- [Source repository](https://github.com/alibaba-fusion/next)
- [HTML version](https://canirequire.com/package/@alifd/next/)
- [JSON version](https://canirequire.com/package/@alifd/next.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.