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

Introduce an ag-charts-core package #3328

Merged
merged 6 commits into from
Jan 7, 2025
Merged

Introduce an ag-charts-core package #3328

merged 6 commits into from
Jan 7, 2025

Conversation

iMoses
Copy link
Contributor

@iMoses iMoses commented Jan 6, 2025

A new internal package to share utilities and core functionality between the community and enterprise packages, to improve our tree-shaking abilities.

@iMoses iMoses requested review from alantreadway and a team as code owners January 6, 2025 14:20
"dependencies": {},
"devDependencies": {},
"publishConfig": {
"access": "public"
Copy link
Member

Choose a reason for hiding this comment

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

Can we mark this as private, to avoid accidental publishing?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My concern was that it may cause issues with the way we publish packages, but I can set it private and we can find out if it does 😅

Copy link
Member

Choose a reason for hiding this comment

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

Yes, I'd prefer that way around. We publish to the private Verdaccio routinely, so I would hope any issues in that respect should show up there; if ag-charts-core is a devDependency I don't foresee any issue with publishing of dependents either?

On another note, as long as we don't generate a .tgz when nx pack --prod is run, then nothing in the publishing pipeline should care AFAIK

Copy link
Member

Choose a reason for hiding this comment

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

As a heads-up, I followed up by removing the package and package:verify targets to ensure we don't generate publishable artifacts: 45b0457

Copy link
Member

@alantreadway alantreadway left a comment

Choose a reason for hiding this comment

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

LGTM

@alantreadway alantreadway merged commit 3606616 into latest Jan 7, 2025
28 checks passed
@alantreadway alantreadway deleted the imoses/tree-shake branch January 7, 2025 13:06
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