@onbeam/biome-config
Advanced tools
The default biome config used throughout all Beam packages and apps. Used to extend upon in your local biome configuration file.
The default biome config used throughout all Beam packages and apps. Used to extend upon in your local biome configuration file.
Install the package using your preferred package manager:
npm install @onbeam/biome-config --save-dev
# or
yarn add @onbeam/biome-config --dev
# or
pnpm add @onbeam/biome-config -D
To keep all @onbeam packages updated, you can use the CLI:
npx @onbeam/cli update -d [directory]
After installing this package, simply extend your biome.json config file with the @onbeam/biome-config default configuration:
{
"$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
"extends": ["./node_modules/@onbeam/biome-config/biome.json"]
}
@onbeam packagesThat's it! Happy coding! 🌈
FAQs
The default biome config used throughout all Beam packages and apps. Used to extend upon in your local biome configuration file.
The npm package @onbeam/biome-config receives a total of 325 weekly downloads. As such, @onbeam/biome-config popularity was classified as not popular.
We found that @onbeam/biome-config demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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.