-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path.prettierignore
148 lines (113 loc) · 4.05 KB
/
.prettierignore
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
####################################################
# .prettierignore Configuration File
####################################################
# Purpose:
# The .prettierignore file is used to specify which files and directories
# should be ignored by Prettier, the code formatting tool. Ignoring these files
# ensures that Prettier does not format files that are automatically generated,
# or where formatting is otherwise unnecessary or undesirable, maintaining a clean
# and consistent code style where it matters most.
####################################################
# IDE AND CODE EDITOR SETTINGS
####################################################
# Purpose:
# Configuration files generated by IDEs and editors are often user-specific
# and should not be formatted. This prevents formatting conflicts and maintains
# individual workspace settings.
# JetBrains IDEA/Android Studio project settings.
.idea/
# macOS-specific file created by Finder for file metadata.
.DS_Store
####################################################
# DEPENDENCY DIRECTORIES
####################################################
# Purpose:
# Directories like `node_modules` or `.yarn/` contain installed dependencies
# which should not be formatted. These directories are regenerated by package
# managers and are not manually maintained.
# Installed Node.js project dependencies.
/node_modules
# Yarn lockfile, cache, and plugin data.
.yarn/
# Plug'n'Play manifest and JavaScript file.
.pnp
.pnp.js
# Cached install state for Yarn berry.
.yarn/install-state.gz
####################################################
# BUILD OUTPUTS
####################################################
# Purpose:
# Build artifacts and compiled code are generated automatically during
# development or production builds and should not be formatted.
# General output folder for build artifacts.
/build
# Next.js build directory.
.next/
# Generic folder for production deployments.
.out/
####################################################
# LOG FILES
####################################################
# Purpose:
# Log files contain runtime and error information and are not relevant
# for code formatting.
# Generic directory for logs and specific log files.
logs/
*.log
logs*.json
docker.log
npm-debug.log*
yarn-debug.log*
####################################################
# ENVIRONMENT VARIABLE CONFIGURATIONS
####################################################
# Purpose:
# Environment configuration files contain sensitive data and specific
# settings that should not be altered by formatting tools.
# All environment variable files.
.env
.env.development
.env.test
.env.staging
.env.uat
.env.production
.env*.local
####################################################
# DOCUMENTATION
####################################################
# Purpose:
# Documentation often follows a specified format that should not be altered
# by formatting tools to ensure their structured content remains intact.
# General documentation directory and specific documentation files.
/documentation/
SECURITY.md
CHANGELOG.md
src/modules/api/documentation/
####################################################
# VERCEL CONFIGURATION
####################################################
# Purpose:
# Vercel deployment configuration should not be altered by formatting tools
# as it is specific to deployment environments.
# Vercel configuration files.
.vercel
####################################################
# MISCELLANEOUS
####################################################
# Purpose:
# Miscellaneous files that do not fit other categories but are typically
# unnecessary for formatting.
# TypeScript build information and Next.js types.
*.tsbuildinfo
next-env.d.ts
# Private keys and sensitive files.
*.pem
####################################################
# LOCAL FILE UPLOADS
####################################################
# Purpose:
# Files uploaded by users during development are stored temporarily and
# should not be formatted to avoid conflicts or unauthorized access.
# Temporary storage for user-uploaded files.
/public/assets