Our development setup assumes a LINUX/BSD environemnt.
- Install Node v10.0.0 or higher.
- Install Yarn package manager
https://yarnpkg.com/en/docs/install
v1.10 or higher. - Fork the upstream repo
https://github.com/box/box-ui-elements
via github. - Clone your fork locally
git clone [email protected]:[YOUR GITHUB USERNAME]/box-ui-elements.git
. - Navigate to the cloned folder
cd box-ui-elements
. - Add the upstream repo to your remotes
git remote add upstream [email protected]:box/box-ui-elements.git
. - Verify your remotes are properly set up
git remote -v
. You should pull updates from theupstream
box repo and push changes to your forkorigin
.
A published version of the style guide can be seen at https://opensource.box.com/box-ui-elements/. The style guide uses live demo data within the UI Elements. Due to security restrictions this data is read-only. You can run a local version of the style guide as follows:
- Start the style guide server via
yarn start
(or viayarn start:examples:legacy
, to include support for IE 11). - Navigate to
http://localhost:6060/
to see the UI Elements in action. If testing on a different machine or VM, you can instead use the IP address shown on your terminal window.
NOTE: This note applies to testing top level UI Elements only and not the lower level components. If you want to use your own live data for the style guide, then start the style guide server using your own developer auth token and a file or folder ID via
TOKEN=<YOUR_TOKEN> FILEID=<YOUR_FILE_ID> yarn start
orTOKEN=<YOUR_TOKEN> FOLDERID=<YOUR_FOLDER_ID> yarn start
To test the Box UI Elements with your own project use local Yarn linking.
- In the UI Elements project run
yarn link
as a one time setup. - In UI Elements project run
yarn start:npm
which starts a local npm build in watch mode. - In your parent project run
yarn link box-ui-elements
every time you plan to use the local linked version. - Run your parent project's build.
yarn start
to launch a local style guide examples server. Uses demo live data for Elements.yarn start:examples:legacy
same as above, but with IE 11 support.yarn start:npm
to symlink Elements viayarn link
to a parent project.yarn start:dev
to launch a local webpack dev server. Uses your own data for Elements.yarn lint
to lint js and css.yarn lint:js --fix
to lint js and fix issues.yarn lint:css --fix
to lint styles and fix issues.yarn test
to launch tests with jest.yarn test --watch
to launch tests with jest in watch mode.yarn test --coverage
to launch tests with jest with coverage.yarn release
to run a release.
For more script commands see package.json
. Test coverage reports are available under reports/coverage.
Install the following plugins in your preferred editor
- Editor Config (standardizes basic editor configuration)
- ESLint (Javascript linting)
- Stylelint (CSS linting)
- Prettier (Javscript formatting)
- Sass (Stylesheets)
- Babel (Transpiler)
Under most circumstances you should be using the style guide as mentioned earlier. This section is primarily for testing the Box UI Elements embedded in a custom HTML page with your own box data and auth token. For this, launch a local webpack dev server via yarn start:dev
and navigate to http://localhost:8080/
. HTML test files for local development are located inside the test folder.
- Open a test file, such as http://localhost:8080/test/sidebar.html
- When prompted, enter a file id and developer token.
- Developer tokens can be created at https://app.box.com/developers/console.
- Select
Custom App
and chooseOauth 2.0 with JWT (Server Authentication)
. - Select
View Your App
>Configuration
>CORS Domains
and addhttp://localhost:8080
to the domain whitelist. Save the configuration. - The developer token will be regenerated once the configuration is saved. Copy the token and paste into the prompt in the localhost test page. The token will be valid for an hour; return to the app configuration page to generate a new token.
- For additional information about developing on the Box Platform, see the Platform docs.
The project is setup with Jest for unit testing. For debugging follow instructions provided in the jest documentation.