jonahsnider/prettier-config-xo

Prettier config that follows the XO code style.

prettier-config-xo

Prettier config that follows the XO code style.

Usage

Default config

Add the prettier property to your package.json.

{
	"name": "my-cool-library",
	"version": "1.0.0",
	"prettier": "prettier-config-xo"
}

Extending the configuration

// prettier.config.js, or some other file
module.exports = {
	...require('prettier-config-xo'),
	semi: false,
};

Spaces

You can use spaces instead of tabs with the space config:

module.exports = require('prettier-config-xo/space');

prettier-config-xo's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• build(deps): update typescript-xo (typescript, xo)
• build(deps): update dependency ava to v6
• build(deps): update dependency semantic-release to v23
• build(deps): update yarn to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/ci.yml

• actions/checkout v4
• actions/setup-node v4
• actions/upload-artifact v4
• actions/checkout v4
• actions/cache v4
• actions/checkout v4
• actions/setup-node v4
• actions/checkout v4
• actions/setup-node v4
• codecov/codecov-action v4
• actions/checkout v4
• actions/setup-node v4

npm

package.json

• @istanbuljs/nyc-config-typescript 1.0.2
• @jonahsnider/prettier-config 1.1.2
• @jonahsnider/xo-config 5.3.0
• @semantic-release/exec 6.0.3
• @types/prettier 3.0.0
• ava 5.3.1
• eslint-plugin-prettier 5.1.3
• nyc 15.1.0
• prettier 3.2.5
• semantic-release 22.0.12
• source-map-support 0.5.21
• ts-node 10.9.2
• typescript 5.3.3
• xo 0.56.0
• node >=10.13.0
• yarn 3.8.1

---

• Check this box to trigger a request for Renovate to run again on this repository

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (@jonahsnider)

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀