[Tooling] Add @esri/calcite-ui-icons to the monorepo packages
#9255
Assignees
Labels
4 - verified
Issues that have been released and confirmed resolved.
estimate - 5
A few days of work, definitely requires updates to tests.
p - medium
Issue is non core or affecting less that 60% of people using the library
tooling
Issues relating to build system fixes or improvements.
Milestone
Comments
geospatialem
added
tooling
13 tasks
geospatialem
modified the milestones:
2024-05-28 - May Main Release,
2024-06-25 - Jun Maintenance Release
geospatialem
modified the milestones:
2024-06-25 - Jun Release,
2024-07-30 - Jul Release
benelan
added
2 - in development
benelan
added a commit
that referenced
this issue
Jul 30, 2024
**Related Issue:** #9255 ## Summary Good news, everyone! `@esri/calcite-ui-icons` is joining the Calcite Design System monorepo. This change will ensure Calcite components always uses the latest and greatest version of the icons. Additionally, the icons will benefit from the monorepo's continuous integration, including automatic changelog generation and deployment. This will give the designers more time to do what they do best! Some much needed cleanup was accomplished during this transition. The following items will no longer be [published to npm](https://unpkg.com/browse/@esri/[email protected]/): ``` .github/* CONTRIBUTE.md bin/build.js bin/cli.js bin/convert-mobile.js bin/optimize.js bin/path-data.js bin/server.js bin/templates/* bower.json docs/app.js docs/index.html docs/resources/* launch-calcite.command launch-meridian.command ``` Additionally, the autogenerated, build files will not longer be committed into version control. This includes: ``` docs/icons.json index.d.ts index.js js/* sprite-16.svg sprite-24.svg sprite-32.svg ``` These files can be generated via `npm run build`. The build files will be attached to GitHub releases for users who do not consume the icons via NPM. Note that I removed `bower.json` since [they recommended](https://bower.io/blog/2017/how-to-migrate-away-from-bower/) using other software back in 2017, and there hasn't been any activity in the [repo](https://github.com/bower/bower) for a few years now. However, I'm open to deprecating bower support and removing it in the next major release if people prefer that route. Release-As: 3.30.0
benelan
added
3 - installed
|
Installed and assigned for verification. |
calcite-admin
pushed a commit
that referenced
this issue
Jul 30, 2024
**Related Issue:** #9255 ## Summary Good news, everyone! `@esri/calcite-ui-icons` is joining the Calcite Design System monorepo. This change will ensure Calcite components always uses the latest and greatest version of the icons. Additionally, the icons will benefit from the monorepo's continuous integration, including automatic changelog generation and deployment. This will give the designers more time to do what they do best! Some much needed cleanup was accomplished during this transition. The following items will no longer be [published to npm](https://unpkg.com/browse/@esri/[email protected]/): ``` .github/* CONTRIBUTE.md bin/build.js bin/cli.js bin/convert-mobile.js bin/optimize.js bin/path-data.js bin/server.js bin/templates/* bower.json docs/app.js docs/index.html docs/resources/* launch-calcite.command launch-meridian.command ``` Additionally, the autogenerated, build files will not longer be committed into version control. This includes: ``` docs/icons.json index.d.ts index.js js/* sprite-16.svg sprite-24.svg sprite-32.svg ``` These files can be generated via `npm run build`. The build files will be attached to GitHub releases for users who do not consume the icons via NPM. Note that I removed `bower.json` since [they recommended](https://bower.io/blog/2017/how-to-migrate-away-from-bower/) using other software back in 2017, and there hasn't been any activity in the [repo](https://github.com/bower/bower) for a few years now. However, I'm open to deprecating bower support and removing it in the next major release if people prefer that route. Release-As: 3.30.0
|
🍡 Verified locally on |
DitwanP
added
4 - verified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Add the calcite-ui-icons repo, to the Calcite monorepo packages.
Part of the monorepo package epic from #7122
Desired Outcome
Adding more Calcite packages to the repo and splitting existing functionality into encapsulated workspaces will improve maintainability and discoverability.
Resources
Additional discussion and context is also linked in #7122.
The text was updated successfully, but these errors were encountered: