npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@nextcloud/prettier-config

v1.1.0

Published

Shared stylistic rules for Nextcloud apps and libraries

Downloads

400

Readme

Nextcloud Prettier configuration

This provides a shared configuration for Nextcloud apps and libraries to have consistent stylistic rules. Using stylistic rules in linters is not recommended as linters are for finding bugs while prettier is for code style. Moreover ESLint and StyleLint both deprecate and remove stylistic rules, as a replacement using Prettier is recommended.

Setup

Prepare ESLint

If you are using ESLint you should enable the eslint-config-prettier configuration which disables all ESLint rules that conflict with Prettier. A detailed description can be found here: github.com/prettier/eslint-config-prettier.

In short, this should be your ESLint config:

{
	"extends": [
		"@nextcloud",
		"prettier" // < this needs to be the last one to override all previous
	]
}

If you still get errors about Vue files, you need to adjust your ESLint config like the following: (this will be fixed once the Nextcloud ESLint config support flat configs)

"extends": [
		"@nextcloud",
		"prettier"
	],
	"overrides": [
		{
			"files": ["**/*.vue"],
			"rules": {
				"vue/first-attribute-linebreak": "off"
			}
		}
	]

Prepare StyleLint

Stylelint already removed all stylistic rules, so make sure to use @nextcloud/stylelint-config 3+ together with stylelint 16+.

Configure Prettier

Install this configuration using:

npm install --save-dev @nextcloud/prettier-config

Either configure Prettier within your package.json:

{
	"name": "nextcloud-app",
	"version": "1.33.7",
	"prettier": "@nextcloud/prettier-config"
}

Or in a dedicated .prettierrc.json:

"@nextcloud/prettier-config"

You should create a .prettierignore file in your project root to allow simply using prettier . or prettier --write ., the format is very similar to .gitignore. For a Nextcloud app the file could look like this:

# version control systems directories
**/.git
**/.svn
**/.hg

# 3rdparty dependencies
**/node_modules
**/vendor

# Compiled JS output
js/

# PHP
lib/
**/*.php