# Checkbox (DEPRECATED) > **WARNING:** This component is deprecated and is no longer supported. Please migrate to the new [Auro Formkit](https://www.npmjs.com/package/@aurodesignsystem/auro-formkit) instead. `` is a [HTML custom element](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements) for the purpose of allowing users to select one or more options of a limited number of choices. ## UI development browser support For the most up to date information on [UI development browser support](https://auro.alaskaair.com/support/browsersSupport) ## Install [](https://github.com/AlaskaAirlines/auro-checkbox/actions/workflows/testPublish.yml) [](https://www.npmjs.com/package/@aurodesignsystem/auro-checkbox) [](https://www.apache.org/licenses/LICENSE-2.0)  ```shell $ npm i @aurodesignsystem/auro-checkbox ``` Installing as a direct, dev or peer dependency is up to the user installing the package. If you are unsure as to what type of dependency you should use, consider reading this [stack overflow](https://stackoverflow.com/questions/18875674/whats-the-difference-between-dependencies-devdependencies-and-peerdependencies) answer. ### Design Token CSS Custom Property dependency The use of any Auro custom element has a dependency on the [Auro Design Tokens](https://auro.alaskaair.com/getting-started/developers/design-tokens). ### Define dependency in project component Defining the component dependency within each component that is using the `` component. ```js import "@aurodesignsystem/auro-checkbox"; ``` **Reference component in HTML** ```html Form label goes here Checkbox option Checkbox option Checkbox option Checkbox option ``` ## Install bundled assets from CDN In cases where the project is not able to process JS assets, there are pre-processed assets available for use. See -- `auro-checkbox__bundled.js` for modern browsers. Legacy browsers such as IE11 are no longer supported. **WARNING!** When installing into your application environment, DO NOT use `@latest` for the requested version. Risks include unknown MAJOR version releases and instant adoption of any new features and possible bugs without developer knowledge. The `@latest` wildcard should NEVER be used for production customer-facing applications. You have been warned. ### Bundle example code ```html ``` ## auro-checkbox use cases The `` element should be used in situations where users may: * Be filling out a form * Need to select one or more options ## API Code Examples ### Default auro-checkbox ```html Form label goes here Checkbox option Checkbox option Checkbox option Checkbox option ``` ## Development In order to develop against this project, if you are not part of the core team, you will be required to fork the project prior to submitting a pull request. Please be sure to review the [contribution guidelines](https://auro.alaskaair.com/contributing) for this project. Please make sure to **pay special attention** to the **conventional commits** section of the document. ### Start development environment Once the project has been cloned to your local resource and you have installed all the dependencies you will need to open a shell session to run the **dev server**. ```shell $ npm run dev ``` Open [localhost:8000](http://localhost:8000/) If running separate sessions is preferred, please run the following commands in individual terminal shells. ```shell $ npm run build:watch $ npm run serve ``` ### API generation The custom element API file is generated in the build and committed back to the repo with a version change. If the API doc has changed without a version change, author's are to run `npm run build:api` to generate the doc and commit to version control. ### Testing Automated tests are required for every Auro component. See `.\test\auro-checkbox.test.js` for the tests for this component. Run `npm test` to run the tests and check code coverage. Tests must pass and meet a certain coverage threshold to commit. See [the testing documentation](https://auro.alaskaair.com/support/tests) for more details. ### Bundled assets Bundled assets are only generated in the remote and not merged back to this repo. To review and/or test a bundled asset locally, run `$ npm run bundler` to generate assets.