Skip to content

Release 2.3.3#656

Merged
wuda-io merged 15 commits intomainfrom
v2-dev
Apr 12, 2026
Merged

Release 2.3.3#656
wuda-io merged 15 commits intomainfrom
v2-dev

Conversation

@wuda-io
Copy link
Copy Markdown
Member

@wuda-io wuda-io commented Apr 12, 2026

Proposed changes

Screenshots (if appropriate) or codepen:

Types of changes

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

  • I have read the CONTRIBUTING document.
  • My commit messages follows the conventional commit format
  • My change requires a change to the documentation, and updated it accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

gselderslaghs and others added 15 commits February 19, 2026 21:52
chore: refactor normalize in dependency tree
The exports field previously only mapped the JS entry points, which
caused bundlers that enforce the Node.js package exports spec (esbuild,
Vite, webpack 5, Rollup) to block any sub-path import not explicitly
listed -- including the CSS and Sass files that are physically present
in the package.

Add wildcard export patterns for ./dist/css/*, ./sass/* and
./components/* so that imports like:

  import '@materializecss/materialize/dist/css/materialize.min.css';
  import '@materializecss/materialize/sass/materialize.scss';
  import { Button } from '@materializecss/materialize/components/buttons/button.mjs';

resolve correctly in all spec-compliant bundlers.

Also add components/ to the files array so component sub-paths are
included in the published package.

The existing "style" and "sass" top-level fields are unaffected and
continue to work for bundlers that use those fields (e.g. webpack
mainFields resolution).

Closes #653
fix: expose CSS, Sass and component sub-paths in package.json exports
@wuda-io wuda-io merged commit 550539d into main Apr 12, 2026
1 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants