stp-ui-kit 0.0.45 → 0.0.46

package/README.md

@@ -1,93 +1,93 @@
-# stp-ui-kit
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.com/smartest-prep/stp-ui-kit.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.com/smartest-prep/stp-ui-kit/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+# stp-ui-kit
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://gitlab.com/smartest-prep/stp-ui-kit.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://gitlab.com/smartest-prep/stp-ui-kit/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

package/dist/banners/Sat.svg

@@ -1,3 +1,3 @@
-<svg width="24" height="40" viewBox="0 0 24 40" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M18.7133 0L0 22.4506H8.63211L5.28671 40L24 17.5494H15.3679L18.7133 0Z" fill="#5EEAD4"/>
-</svg>
+<svg width="24" height="40" viewBox="0 0 24 40" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M18.7133 0L0 22.4506H8.63211L5.28671 40L24 17.5494H15.3679L18.7133 0Z" fill="#5EEAD4"/>
+</svg>

package/dist/banners/SatFinished.svg

@@ -1,3 +1,3 @@
-<svg width="24" height="40" viewBox="0 0 24 40" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M18.7133 0L0 22.4506H8.63211L5.28671 40L24 17.5494H15.3679L18.7133 0Z" fill="#5B21B6"/>
-</svg>
+<svg width="24" height="40" viewBox="0 0 24 40" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M18.7133 0L0 22.4506H8.63211L5.28671 40L24 17.5494H15.3679L18.7133 0Z" fill="#5B21B6"/>
+</svg>

package/dist/components/Typography/Typography.d.ts

@@ -3,5 +3,6 @@ export interface TypographyProps {
     variant?: "heading-xl" | "heading-lg" | "heading-md" | "heading-sm" | "heading-xs" | "body-lg" | "body-md" | "body-sm";
     className?: string;
     children: ReactNode;
+    weight?: "regular" | "semibold" | "bold" | "medium";
 }
-export declare const Typography: ({ variant, className, children, }: TypographyProps) => import("react/jsx-runtime").JSX.Element;
+export declare const Typography: ({ variant, className, children, weight, }: TypographyProps) => import("react/jsx-runtime").JSX.Element;

package/dist/icons/ArrowLine.svg

@@ -1,3 +1,3 @@
-<svg width="20" height="36" viewBox="0 0 20 36" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M9 0H10.5V12.95C10.5 13.8025 10.5006 14.3967 10.5384 14.8593C10.5755 15.3132 10.6446 15.574 10.7452 15.7715C10.961 16.1948 11.3052 16.539 11.7285 16.7548C11.926 16.8554 12.1868 16.9245 12.6407 16.9616C13.1033 16.9994 13.6975 17 14.55 17H16.9393L15.2197 15.2803C14.9268 14.9874 14.9268 14.5126 15.2197 14.2197C15.5126 13.9268 15.9874 13.9268 16.2803 14.2197L19.2803 17.2197C19.5732 17.5126 19.5732 17.9874 19.2803 18.2803L16.2803 21.2803C15.9874 21.5732 15.5126 21.5732 15.2197 21.2803C14.9268 20.9874 14.9268 20.5126 15.2197 20.2197L16.9393 18.5H14.5179C13.705 18.5 13.0494 18.5 12.5185 18.4566C11.9719 18.412 11.4918 18.3176 11.0475 18.0913C10.3419 17.7317 9.76825 17.1581 9.40873 16.4525C9.18239 16.0082 9.08803 15.5281 9.04336 14.9815C8.99999 14.4506 8.99999 13.795 9 12.9821V0Z" fill="#868892"/>
-</svg>
+<svg width="20" height="36" viewBox="0 0 20 36" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M9 0H10.5V12.95C10.5 13.8025 10.5006 14.3967 10.5384 14.8593C10.5755 15.3132 10.6446 15.574 10.7452 15.7715C10.961 16.1948 11.3052 16.539 11.7285 16.7548C11.926 16.8554 12.1868 16.9245 12.6407 16.9616C13.1033 16.9994 13.6975 17 14.55 17H16.9393L15.2197 15.2803C14.9268 14.9874 14.9268 14.5126 15.2197 14.2197C15.5126 13.9268 15.9874 13.9268 16.2803 14.2197L19.2803 17.2197C19.5732 17.5126 19.5732 17.9874 19.2803 18.2803L16.2803 21.2803C15.9874 21.5732 15.5126 21.5732 15.2197 21.2803C14.9268 20.9874 14.9268 20.5126 15.2197 20.2197L16.9393 18.5H14.5179C13.705 18.5 13.0494 18.5 12.5185 18.4566C11.9719 18.412 11.4918 18.3176 11.0475 18.0913C10.3419 17.7317 9.76825 17.1581 9.40873 16.4525C9.18239 16.0082 9.08803 15.5281 9.04336 14.9815C8.99999 14.4506 8.99999 13.795 9 12.9821V0Z" fill="#868892"/>
+</svg>

package/dist/icons/ParentLine.svg

@@ -1,3 +1,3 @@
-<svg width="2" height="6" viewBox="0 0 2 6" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M0 0.75C0 0.335786 0.335786 0 0.75 0C1.16421 0 1.5 0.335786 1.5 0.75V6H0V0.75Z" fill="#868892"/>
-</svg>
+<svg width="2" height="6" viewBox="0 0 2 6" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M0 0.75C0 0.335786 0.335786 0 0.75 0C1.16421 0 1.5 0.335786 1.5 0.75V6H0V0.75Z" fill="#868892"/>
+</svg>

package/dist/icons/SideLine.svg

@@ -1,3 +1,3 @@
-<svg width="20" height="36" viewBox="0 0 20 36" fill="none" xmlns="http://www.w3.org/2000/svg">
-<rect x="9" width="1.5" height="36" fill="#868892"/>
-</svg>
+<svg width="20" height="36" viewBox="0 0 20 36" fill="none" xmlns="http://www.w3.org/2000/svg">
+<rect x="9" width="1.5" height="36" fill="#868892"/>
+</svg>

package/dist/icons/decorativeIcons/Alert.svg

@@ -1,11 +1,11 @@
-<svg width="80" height="80" viewBox="0 0 80 80" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M40 73.3334C58.4095 73.3334 73.3333 58.4095 73.3333 40C73.3333 21.5905 58.4095 6.66669 40 6.66669C21.5905 6.66669 6.66663 21.5905 6.66663 40C6.66663 58.4095 21.5905 73.3334 40 73.3334Z" fill="url(#paint0_linear_970_832)"/>
-<path d="M40 26.6667V40" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
-<path d="M40 53.3334H40.0333" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
-<defs>
-<linearGradient id="paint0_linear_970_832" x1="40" y1="6.66669" x2="40" y2="73.3334" gradientUnits="userSpaceOnUse">
-<stop stop-color="#FEF3C7"/>
-<stop offset="1" stop-color="#F59E0B"/>
-</linearGradient>
-</defs>
-</svg>
+<svg width="80" height="80" viewBox="0 0 80 80" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M40 73.3334C58.4095 73.3334 73.3333 58.4095 73.3333 40C73.3333 21.5905 58.4095 6.66669 40 6.66669C21.5905 6.66669 6.66663 21.5905 6.66663 40C6.66663 58.4095 21.5905 73.3334 40 73.3334Z" fill="url(#paint0_linear_970_832)"/>
+<path d="M40 26.6667V40" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M40 53.3334H40.0333" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
+<defs>
+<linearGradient id="paint0_linear_970_832" x1="40" y1="6.66669" x2="40" y2="73.3334" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FEF3C7"/>
+<stop offset="1" stop-color="#F59E0B"/>
+</linearGradient>
+</defs>
+</svg>

package/dist/icons/decorativeIcons/Error.svg

@@ -1,11 +1,11 @@
-<svg width="80" height="80" viewBox="0 0 80 80" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M40 73.3334C58.4095 73.3334 73.3333 58.4095 73.3333 40C73.3333 21.5905 58.4095 6.66669 40 6.66669C21.5905 6.66669 6.66663 21.5905 6.66663 40C6.66663 58.4095 21.5905 73.3334 40 73.3334Z" fill="url(#paint0_linear_970_956)"/>
-<path d="M50 30L30 50" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
-<path d="M30 30L50 50" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
-<defs>
-<linearGradient id="paint0_linear_970_956" x1="40" y1="6.66669" x2="40" y2="73.3334" gradientUnits="userSpaceOnUse">
-<stop stop-color="#FEE2E2"/>
-<stop offset="1" stop-color="#EF4444"/>
-</linearGradient>
-</defs>
-</svg>
+<svg width="80" height="80" viewBox="0 0 80 80" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M40 73.3334C58.4095 73.3334 73.3333 58.4095 73.3333 40C73.3333 21.5905 58.4095 6.66669 40 6.66669C21.5905 6.66669 6.66663 21.5905 6.66663 40C6.66663 58.4095 21.5905 73.3334 40 73.3334Z" fill="url(#paint0_linear_970_956)"/>
+<path d="M50 30L30 50" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
+<path d="M30 30L50 50" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
+<defs>
+<linearGradient id="paint0_linear_970_956" x1="40" y1="6.66669" x2="40" y2="73.3334" gradientUnits="userSpaceOnUse">
+<stop stop-color="#FEE2E2"/>
+<stop offset="1" stop-color="#EF4444"/>
+</linearGradient>
+</defs>
+</svg>

package/dist/icons/decorativeIcons/Locked.svg

@@ -1,10 +1,10 @@
-<svg width="80" height="80" viewBox="0 0 80 80" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path fill-rule="evenodd" clip-rule="evenodd" d="M29.9827 13.3153C32.6394 10.6586 36.2428 9.16602 40 9.16602C43.7572 9.16602 47.3606 10.6586 50.0173 13.3153C52.6741 15.9721 54.1667 19.5754 54.1667 23.3327V33.3327C54.1667 33.3331 54.1667 33.3335 54.1667 33.334H25.8333C25.8333 33.3335 25.8333 33.3331 25.8333 33.3327V23.3327C25.8333 19.5754 27.3259 15.9721 29.9827 13.3153ZM20.8333 33.334C20.8333 33.3335 20.8333 33.3331 20.8333 33.3327V23.3327C20.8333 18.2494 22.8527 13.3742 26.4471 9.7798C30.0416 6.18535 34.9167 4.16602 40 4.16602C45.0833 4.16602 49.9584 6.18535 53.5529 9.7798C57.1473 13.3742 59.1667 18.2494 59.1667 23.3327V33.3327C59.1667 33.3331 59.1667 33.3335 59.1667 33.334H63.3333C67.0152 33.334 70 36.3188 70 40.0007V66.6673C70 70.3492 67.0152 73.334 63.3333 73.334H16.6667C12.9848 73.334 10 70.3492 10 66.6673V40.0007C10 36.3188 12.9848 33.334 16.6667 33.334H20.8333Z" fill="url(#paint0_linear_995_7796)"/>
-<path d="M40 56.6667C41.8409 56.6667 43.3333 55.1743 43.3333 53.3333C43.3333 51.4924 41.8409 50 40 50C38.159 50 36.6666 51.4924 36.6666 53.3333C36.6666 55.1743 38.159 56.6667 40 56.6667Z" fill="white" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
-<defs>
-<linearGradient id="paint0_linear_995_7796" x1="40" y1="4.16602" x2="40" y2="73.334" gradientUnits="userSpaceOnUse">
-<stop stop-color="#E4E8ED"/>
-<stop offset="1" stop-color="#868892"/>
-</linearGradient>
-</defs>
-</svg>
+<svg width="80" height="80" viewBox="0 0 80 80" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path fill-rule="evenodd" clip-rule="evenodd" d="M29.9827 13.3153C32.6394 10.6586 36.2428 9.16602 40 9.16602C43.7572 9.16602 47.3606 10.6586 50.0173 13.3153C52.6741 15.9721 54.1667 19.5754 54.1667 23.3327V33.3327C54.1667 33.3331 54.1667 33.3335 54.1667 33.334H25.8333C25.8333 33.3335 25.8333 33.3331 25.8333 33.3327V23.3327C25.8333 19.5754 27.3259 15.9721 29.9827 13.3153ZM20.8333 33.334C20.8333 33.3335 20.8333 33.3331 20.8333 33.3327V23.3327C20.8333 18.2494 22.8527 13.3742 26.4471 9.7798C30.0416 6.18535 34.9167 4.16602 40 4.16602C45.0833 4.16602 49.9584 6.18535 53.5529 9.7798C57.1473 13.3742 59.1667 18.2494 59.1667 23.3327V33.3327C59.1667 33.3331 59.1667 33.3335 59.1667 33.334H63.3333C67.0152 33.334 70 36.3188 70 40.0007V66.6673C70 70.3492 67.0152 73.334 63.3333 73.334H16.6667C12.9848 73.334 10 70.3492 10 66.6673V40.0007C10 36.3188 12.9848 33.334 16.6667 33.334H20.8333Z" fill="url(#paint0_linear_995_7796)"/>
+<path d="M40 56.6667C41.8409 56.6667 43.3333 55.1743 43.3333 53.3333C43.3333 51.4924 41.8409 50 40 50C38.159 50 36.6666 51.4924 36.6666 53.3333C36.6666 55.1743 38.159 56.6667 40 56.6667Z" fill="white" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
+<defs>
+<linearGradient id="paint0_linear_995_7796" x1="40" y1="4.16602" x2="40" y2="73.334" gradientUnits="userSpaceOnUse">
+<stop stop-color="#E4E8ED"/>
+<stop offset="1" stop-color="#868892"/>
+</linearGradient>
+</defs>
+</svg>

package/dist/icons/decorativeIcons/Success.svg

@@ -1,10 +1,10 @@
-<svg width="80" height="80" viewBox="0 0 80 80" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M40 73.3334C58.4095 73.3334 73.3334 58.4095 73.3334 40C73.3334 21.5905 58.4095 6.66669 40 6.66669C21.5905 6.66669 6.66669 21.5905 6.66669 40C6.66669 58.4095 21.5905 73.3334 40 73.3334Z" fill="url(#paint0_linear_970_544)"/>
-<path d="M30 40L36.6667 46.6666L50 33.3333" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
-<defs>
-<linearGradient id="paint0_linear_970_544" x1="40" y1="6.66669" x2="40" y2="73.3334" gradientUnits="userSpaceOnUse">
-<stop stop-color="#DCFCE7"/>
-<stop offset="1" stop-color="#22C55E"/>
-</linearGradient>
-</defs>
-</svg>
+<svg width="80" height="80" viewBox="0 0 80 80" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M40 73.3334C58.4095 73.3334 73.3334 58.4095 73.3334 40C73.3334 21.5905 58.4095 6.66669 40 6.66669C21.5905 6.66669 6.66669 21.5905 6.66669 40C6.66669 58.4095 21.5905 73.3334 40 73.3334Z" fill="url(#paint0_linear_970_544)"/>
+<path d="M30 40L36.6667 46.6666L50 33.3333" stroke="white" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
+<defs>
+<linearGradient id="paint0_linear_970_544" x1="40" y1="6.66669" x2="40" y2="73.3334" gradientUnits="userSpaceOnUse">
+<stop stop-color="#DCFCE7"/>
+<stop offset="1" stop-color="#22C55E"/>
+</linearGradient>
+</defs>
+</svg>

package/dist/shared/@types/resources.d.ts

@@ -1,5 +1,5 @@
-interface Resources {
-  common: {};
-}
-
-export default Resources;
+interface Resources {
+  common: {};
+}
+
+export default Resources;

package/dist/shared/i18n/i18next.d.ts

@@ -1,9 +1,11 @@
 import { default as Resources } from '../@types/resources';
 import { AppI18NextNamespace } from './types';
-declare module "i18next" {
-  interface CustomTypeOptions {
-    defaultNS: "all";
-    ns: AppI18NextNamespace;
-    resources: Resources;
-  }
-}
+
+
+declare module "i18next" {
+  interface CustomTypeOptions {
+    defaultNS: "all";
+    ns: AppI18NextNamespace;
+    resources: Resources;
+  }
+}