Skip to content

Regression in @fontsource/poppins v5.2.0 – Imports for Specific Weights and Styles Fail #1032

@ChaseMarcum

Description

@ChaseMarcum

Describe the bug

After updating @fontsource/poppins from v5.1.1 to v5.2.0, importing specific font weights and styles in our React application now results in build errors.

Previously, we imported fonts as follows without issues:

import '@fontsource/poppins/200.css';
import '@fontsource/poppins/300.css';
import '@fontsource/poppins/400-italic.css';
import '@fontsource/poppins/400.css';
import '@fontsource/poppins/500.css';
import '@fontsource/poppins/600.css';
import '@fontsource/poppins/700.css';

Upon upgrading to v5.2.0, we now receive the following Webpack errors:

ERROR in ./src/index.tsx 1:0-37
Module not found: Error: Package path ./200.css is not exported from package @fontsource/poppins (see exports field in package.json)

This occurs for all weight/style imports.

Observed Changes in package.json

The exports field in v5.2.0 now restricts what is accessible:

"exports": {
  ".": { "sass": "./index.css", "default": "./index.css" },
  "./scss": { "sass": "./scss/metadata.scss" }
}

This appears to prevent direct imports of individual weight/style files.

Environment Details

  • Node.js version: 22.14.0
  • Package manager npm and version: 11.1.0
  • Build system: Webpack 5
  • OS: macOS Sequoia 15.3.1

Steps to Reproduce

Imported fonts:

import '@fontsource/poppins/200.css';
import '@fontsource/poppins/300.css';
import '@fontsource/poppins/400-italic.css';
import '@fontsource/poppins/400.css';
import '@fontsource/poppins/500.css';
import '@fontsource/poppins/600.css';
import '@fontsource/poppins/700.css';

Steps to Reproduce

  1. Install @fontsource/[email protected]
  2. Import fonts as shown above
  3. Run npm run build
  4. Observe Webpack errors related to missing exports

Expected behavior

  • Importing weights and styles as separate .css files should continue to work as in previous versions.

Version

5.2.0

OS

macOS Sequoia 15.3.1

Browser

No response

Additional context

Workarounds

For now, we have downgraded to v5.1.1 to restore functionality.

Could you confirm if this change was intentional, or if there's an alternative way to import font weights and styles in v5.2.0?

Thanks for your help!

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions