Welcome to the Topcoder UI Kit!
npm install --save tc-ui-kit or add tc-ui-kit: '0.0.x' to your package.json file
Once installed, put @import topcoder-styles in your top level css file. @import topcoder-styles should only be included once. On every other CSS file that requires access to variables or mixins, put @import topcoder-includes at the top.
Link to live UI Kit soon using the [SC5 styleguide generator] (http://styleguide.sc5.io/). Checkout the [demo] (http://demo.styleguide.sc5.io/) to see what it will look like.
When contributing to this repo, please follow the style guide below. Any changes that are not purely code related must be approved by Vic, and anything added to the repo should be for use across all Topcoder pages. Any page specific images or styles should be added to topcoder-app.
When you're done adding content or making changes, increase the version number in package.json. Push your code up to Github, and run npm publish. Then, in your project that uses tc-ui-kit, run npm update tc-ui-kit. Note that you must have a version number like 0.0.x in your package.json for npm update to work.
When creating new ui components:
tc-FAQs
Topcoder UI Kit
We found that tc-ui-kit demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.