-
Notifications
You must be signed in to change notification settings - Fork 386
npm [email protected] is missing built files #1374
Comments
@metanerd Should I open a ticket to investigate? |
I suggest switching to a newer release version due to npm tags disallowing publishing a lower release version. |
That can't be true. You may not be able to republish a version (I'm not sure) but projects maintain multiple major releases all the time, updating 1.1.0 to 1.1.1 and at the same time having published 2.0.0 and 3.1.0 for example. You may not think it's worth publishing 5.29.3 to fix the broken 5.29.2 and that's fine, but that npm tags won't allow it is not a good reason. I personally just reverted to 5.29.1, however having a broken publicly published package seemed worth reporting (and I'd think it was worth fixing, but that's just me). |
Yes, you are absolutely correct in reporting it. Thank you for that! I ran into some issues before with the way we publish the package. I will however look into it again. |
Thanks @metanerd for your response and letting me know what the cause was, I really appreciate it. |
Summary
npm [email protected] is missing built files
Steps to reproduce
Expected behavior
Same basic set of files as for version 5.29.1 which is:
contents of node_modules/mattermost-redux@5.29.1
Although I'm not sure why the
src
directory is included in the package.Observed behavior
Notice all of the missing build directories (eg.
action_types
,actions
,client
etc.)contents of node_modules/mattermost-redux@5.29.2
Possible fixes
I'm not sure what the normal process that publishes the mattermost_redux package is, but it looks like it was supposed to be built first and wasn't.
The text was updated successfully, but these errors were encountered: