-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: invalid resolution of icon-helpers (#16823)
* fix: invalid resolution of icon-helpers * fix: relocate the incremental-migration-vite example
- Loading branch information
1 parent
14d1896
commit 250923e
Showing
23 changed files
with
4 additions
and
498 deletions.
There are no files selected for viewing
Binary file removed
BIN
-13.6 KB
.yarn/cache/@carbon-feature-flags-npm-0.7.0-7f192756d6-1c311913a2.zip
Binary file not shown.
Binary file removed
BIN
-19.7 MB
.yarn/cache/@carbon-icons-react-npm-10.49.0-38655169d3-d2bd3d4a4c.zip
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-3.99 MB
.yarn/cache/carbon-components-npm-10.58.0-a89302e587-9fc9c7015f.zip
Binary file not shown.
Binary file removed
BIN
-2.35 MB
.yarn/cache/carbon-components-react-npm-7.59.0-3db1ba9c08-39dcad7afe.zip
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-29.9 KB
.yarn/cache/compute-scroll-into-view-npm-1.0.17-708f0ecc3d-9c7b730442.zip
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,51 +1,4 @@ | ||
## Incremental migration | ||
|
||
We have recently released a new version, v11, of our component library and a | ||
common question we receive is if users can adopt v11 incrementally and the | ||
answer is yes! If the burden of migrating to v11 is too big to take on all at | ||
once, but there are features of our latest release you want to take advantage | ||
of, it is likely that you can pull in just the parts you are wanting to use | ||
while keeping the rest of your Carbon usage the same. | ||
|
||
This example illustrates how v11 and v10 work together. | ||
|
||
## Getting Started | ||
|
||
First, run `yarn build` in the root of the `carbon` repository. | ||
|
||
```sh | ||
yarn install && yarn build | ||
``` | ||
|
||
Now, all you need to do is `cd` into the directory and run: | ||
|
||
```sh | ||
yarn install | ||
# or | ||
npm install | ||
|
||
|
||
yarn dev | ||
# or | ||
npm run dev | ||
``` | ||
|
||
This example only takes a little bit of time to start, once it's up and running, | ||
it's very fast. | ||
|
||
Open [http://localhost:5173](http://localhost:5173) with your browser to see the | ||
result. | ||
|
||
## Sass | ||
|
||
First and foremost, if you want to use v11 styles in any capacity, you'll have | ||
to migrate to use `dart-sass`. `node-sass` has been deprecated and we migrated | ||
to `dart-sass` in v11. For more information about migrating, visit our docs | ||
[here](https://github.com/carbon-design-system/carbon/blob/main/docs/migration/v11.md#changing-from-node-sass-to-sass). | ||
|
||
## V10 and V11 | ||
|
||
This example is mainly v10, but it takes advantage of the new Stack component | ||
from v11 and uses v11's StructuredList component 🎉. StructuredList had a major | ||
accessibilty revamp in v11 that you might want to use and this examples shows | ||
you how. | ||
This example has moved to: | ||
https://stackblitz.com/edit/github-gng7o6?file=README.md |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
14 changes: 0 additions & 14 deletions
14
examples/incremental-migration-vite/src/scss/App.module.css
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.