Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add dependencies used in the new dist folder as production dependencies #16649

Closed
wants to merge 2 commits into from

Conversation

filipsobol
Copy link
Member

@filipsobol filipsobol commented Jul 2, 2024

Suggested merge commit message (convention)

Fix: Add dependencies used in the new dist folder as production dependencies instead of devDependencies. Related to #16646.


Additional information

Blocked by ckeditor/ckeditor5-dev#964.

Copy link
Contributor

@pszczesniak pszczesniak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we discussed internally, proabably best solution is to have the dependency-checker task run while preparing the release. This is caused by this, that each package must be built and has to had it's own dist folder. As we know it's not obvious to force it locally, so the best place is to do it on CI while release process is firing.

When some package has not got a dist folder - results of dependency-checker will be wrong.

cc @pomek

@filipsobol
Copy link
Member Author

Will be continued in #16749.

@filipsobol filipsobol closed this Jul 17, 2024
@filipsobol filipsobol deleted the treat-deps-in-dist-folder-as-prod-deps branch July 22, 2024 14:29
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.

2 participants