Closed george-cz closed 4 months ago
Recently I did an upgrade of react-resize-handle, everything worked locally, but it could not be added as a dependency to a project, complaining about invalid path to entry point.
react-resize-handle
With more examination we discovered that there is an extra src directory in the lib folder of the published package (open "lib"): https://www.npmjs.com/package/@fluentui-contrib/react-resize-handle/v/0.3.0?activeTab=code which is not accounted for in the package.json entrypoint. This results in the package being unusable.
src
lib
package.json
For comparison, this is the previous version (open "lib"): https://www.npmjs.com/package/@fluentui-contrib/react-resize-handle/v/0.2.0?activeTab=code
Running build locally seems to produce the correct folder structure.
This probably affects all of the contrib packages and is most likely a result of recent changes in the CI/CD pipeline.
thanks for reporting thisi!
It's a regression introduced by swc bump ( https://github.com/microsoft/fluentui-contrib/pull/191 )
https://github.com/swc-project/cli/issues/281
Recently I did an upgrade of
react-resize-handle
, everything worked locally, but it could not be added as a dependency to a project, complaining about invalid path to entry point.With more examination we discovered that there is an extra
src
directory in thelib
folder of the published package (open "lib"): https://www.npmjs.com/package/@fluentui-contrib/react-resize-handle/v/0.3.0?activeTab=code which is not accounted for in thepackage.json
entrypoint. This results in the package being unusable.For comparison, this is the previous version (open "lib"): https://www.npmjs.com/package/@fluentui-contrib/react-resize-handle/v/0.2.0?activeTab=code
Running build locally seems to produce the correct folder structure.
This probably affects all of the contrib packages and is most likely a result of recent changes in the CI/CD pipeline.