Closed ShakMR closed 1 year ago
The package seems to have an error in the publish step. The generated code in node_modules is not complete:
I also faced this error. Version 5.1.0 only includes library typing.
Getting the same error after upgrading. node_modules missing?
The package seems to have an error in the publish step. The generated code in node_modules is not complete:
In all package versions i.e. ^5.0.0, ^5.0.1, ^5.0.2 and ^5.1.0 after installing it doesn't include lib and parcel folder. Have to downgrade to ^4.6.1 to make it work in application.
The package seems to have an error in the publish step. The generated code in node_modules is not complete:
In all package versions i.e. ^5.0.0, ^5.0.1, ^5.0.2 and ^5.1.0 after installing it doesn't include lib and parcel folder. Have to downgrade to ^4.6.1 to make it work in application.
Version 5.0.2 has the library files. Remove node modules and lock file to install it
The package seems to have an error in the publish step. The generated code in node_modules is not complete:
In all package versions i.e. ^5.0.0, ^5.0.1, ^5.0.2 and ^5.1.0 after installing it doesn't include lib and parcel folder. Have to downgrade to ^4.6.1 to make it work in application.
Version 5.0.2 has the library files. Remove node modules and lock file to install it
Agree only ^5.1.0 has issue
Same. Confirmed with Yarn 3. Downgraded to version 5.0.2 works fine.
I am not sure if this is related to this, but even with version 5.0.2, the following settings failed with single-spa-react
:
moduleResolution: "Bundler"
Changing the moduleResolution
to "Node" is the workaround.
My guess is that this is related to https://github.com/single-spa/single-spa-react/pull/168
The autopublishing feature also might have messed with the folders that were published to npm. I have stopped all the autopublishing and am publishing manually now.
@darshkpatel do you know what could have caused this? I will attempt to replicate this and find a fix, but don't have a lot of work time budgeted for open source right now.
I tried checking out to v5.1.0
tag and running pnpm build
it does generate the parcel and lib folders
What steps do you use to publish manually ?
Ah I misread the issue. I thought the publish error only occurred with the previous versions rather than 5.1.0, and thought the issue was related to the package.json export rather than publishing. I have published version 5.1.1 which has the lib
and parcel
folders
I've confirmed that version 5.1.1 works with a fresh create-single-spa project.
I think the reason 5.1.0 had a bad publish is that I did it from a new computer and something might have been misconfigured. The package.json files
property has lib
and parcel
listed, so I don't know why they weren't included. I published 5.1.1 from my normal work computer and it was fine - pnpm pack
showed that the lib and parcel folders were to be included
After updating 1 hour ago we started getting this error in the build step.