Package
react
Package version
8.122.3
React version
any
Environment
System:
OS: Windows 11 10.0.26100
CPU: (16) x64 AMD EPYC 7763 64-Core Processor
Memory: 19.41 GB / 63.95 GB
Browsers:
Edge: Chromium (133.0.3065.59)
Current Behavior
The 8.122.13 release is missing the dist folder. The 8.122.12 release has it:


This is causing build break for newly generated packages in the SPFx generator:
[16:20:38] Error - sass - src\webparts\helloWorld\components\HelloWorld.module.scss(1,9): error Error: Can't find stylesheet to import.
╷
1 │ @import '~@fluentui/react/dist/sass/References.scss';
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
src\webparts\helloWorld\components\HelloWorld.module.scss 1:9 root stylesheet
Expected Behavior
The dist (and lib) folders should be present.
Reproduction
https://www.npmjs.com/package/@fluentui/react/v/8.122.13?activeTab=code
Steps to reproduce
Go to NPMJS and look at the folder structure:
https://www.npmjs.com/package/@fluentui/react/v/8.122.13?activeTab=code
https://www.npmjs.com/package/@fluentui/react/v/8.122.12?activeTab=code
Are you reporting an Accessibility issue?
None
Suggested severity
Medium - Has workaround
Products/sites affected
SharePoint Framework users
Are you willing to submit a PR to fix?
no
Validations
Package
react
Package version
8.122.3
React version
any
Environment
System: OS: Windows 11 10.0.26100 CPU: (16) x64 AMD EPYC 7763 64-Core Processor Memory: 19.41 GB / 63.95 GB Browsers: Edge: Chromium (133.0.3065.59)Current Behavior
The 8.122.13 release is missing the
distfolder. The8.122.12release has it:This is causing build break for newly generated packages in the SPFx generator:
Expected Behavior
The dist (and lib) folders should be present.
Reproduction
https://www.npmjs.com/package/@fluentui/react/v/8.122.13?activeTab=code
Steps to reproduce
Go to NPMJS and look at the folder structure:
https://www.npmjs.com/package/@fluentui/react/v/8.122.13?activeTab=code
https://www.npmjs.com/package/@fluentui/react/v/8.122.12?activeTab=code
Are you reporting an Accessibility issue?
None
Suggested severity
Medium - Has workaround
Products/sites affected
SharePoint Framework users
Are you willing to submit a PR to fix?
no
Validations