Skip to content

Instantly share code, notes, and snippets.

View montasim's full-sized avatar
💭
𝗟𝗢𝗢𝗞𝗜𝗡𝗚 𝗙𝗢𝗥 𝗡𝗘𝗪 𝗢𝗣𝗣𝗢𝗥𝗧𝗨𝗡𝗜𝗧𝗜𝗘𝗦.

M♢NTΛSIM montasim

💭
𝗟𝗢𝗢𝗞𝗜𝗡𝗚 𝗙𝗢𝗥 𝗡𝗘𝗪 𝗢𝗣𝗣𝗢𝗥𝗧𝗨𝗡𝗜𝗧𝗜𝗘𝗦.
View GitHub Profile
@montasim
montasim / jsdoc.json
Created July 6, 2024 14:29
This configuration ensures that the documentation for your JavaScript project is comprehensive, maintaining high standards of readability and accessibility for developers.
{
"source": {
"include": ["src"],
"includePattern": ".+\\.js$",
"excludePattern": "(build/|node_modules/|documentation/)"
},
"plugins": ["plugins/markdown"],
"templates": {
"cleverLinks": true,
"monospaceLinks": true,
@montasim
montasim / eslint.config.mjs
Created July 6, 2024 14:28
This ESLint configuration is crafted to ensure that the JavaScript code in your project adheres to a set of defined standards and practices, enhancing code quality and maintainability.
/**
* ESLint Configuration File
* @fileoverview This configuration file sets up linting rules and environments for a JavaScript project.
* It includes settings for ECMAScript 2020 features, enforces coding styles, and configures plugins for additional linting capabilities.
*/
export default {
// Specifies the types of files ESLint will lint
files: ['**/*.js', '**/*.jsx', '**/*.ts', '**/*.tsx'],
@montasim
montasim / ecosystem.config.json
Created July 6, 2024 14:26
The ecosystem.config.json file is a configuration file used by PM2, a popular process manager for Node.js applications. This file allows you to define and manage complex application environments with multiple configurations. Below is a detailed overview and description of the settings specified in your ecosystem.config.json file for a library ma…
{
"apps": [
{
"name": "library-management-system-server:production",
"script": "build/server.js",
"instances": 1,
"autorestart": true,
"watch": false,
"time": true,
"exec_mode": "cluster",
@montasim
montasim / .yarnclean
Created July 6, 2024 14:24
Using the .yarnclean file effectively helps maintain a cleaner, more efficient codebase and can be a crucial part of optimizing JavaScript projects that use Yarn as a package manager.
# test directories
__tests__
test
tests
powered-test
# asset directories
docs
doc
website
@montasim
montasim / .versionrc.json
Created July 6, 2024 14:22
Using a .versionrc.json file: Automates Version Management: Automatically handles version increments based on commit types and messages, ensuring consistent versioning that adheres to semantic versioning principles. Streamlines Releases: Simplifies the process of generating changelogs and tagging releases, saving time and reducing human error. E…
{
"types": [
{
"type": "feat",
"section": "Features",
"hidden": false
},
{
"type": "fix",
"section": "Bug Fixes",
@montasim
montasim / .prettierrc
Created July 6, 2024 14:20
Using a .prettierrc file in your project ensures that everyone contributing to the codebase follows the same formatting rules. This eliminates discussions over style in code review, saves time, and reduces inconsistencies that can lead to errors. It can also make it easier for new developers to adhere to project standards from the outset. Pretti…
{
"semi": true,
"singleQuote": true,
"arrowParens": "always",
"trailingComma": "es5",
"bracketSpacing": true,
"tabWidth": 4,
"useTabs": false,
"endOfLine": "crlf",
"overrides": [
@montasim
montasim / .prettierignore
Created July 6, 2024 14:19
Ignoring these files and directories ensures that Prettier only formats the code files you actively develop and maintain, such as .js, .jsx, .ts, .tsx, .css, .html, etc. This helps maintain the integrity and readability of configuration files and directories that either contain generated code, package dependencies, or configuration settings that…
# Ignore artifacts:
.idea
node_modules
build
logs
documentation
@montasim
montasim / .gitattributes
Last active July 6, 2024 14:17
Using a .gitattributes file improves the robustness of a codebase by ensuring that all contributors adhere to defined file handling conventions, regardless of their personal Git configurations or operating systems. This leads to fewer merge conflicts and issues related to improper file handling, and it makes the repository more stable and easier…
# This configuration file is used by Git to handle the line endings and encoding settings for files based on their type.
# It ensures consistent handling of files across different operating systems and environments.
# Set the default behavior, in case people don't have core.autocrlf set.
* text=auto
# Ensures automatic text handling, which normalizes line endings on commit and converts them on checkout.
# Specify line ending settings for specific file types to ensure consistency across platforms.
*.js text eol=crlf # Ensure JavaScript files use CRLF line endings in Windows environments.
*.jsx text eol=crlf # Ensure JSX files use CRLF line endings in Windows environments.
@montasim
montasim / .editorconfig
Last active July 6, 2024 14:15
The purpose of this .editorconfig file is to ensure that all contributors to your project adhere to specified coding and styling standards automatically, minimizing the formatting discrepancies that can occur when different developers with different editing environments work on the same project. This leads to cleaner, more readable code that loo…
# EditorConfig is awesome: https://EditorConfig.org
# top-most EditorConfig file
root = true
# Matches multiple files with brace expansion notation
[*.{js,jsx,ts,tsx}]
charset = utf-8
indent_style = space
indent_size = 4
@montasim
montasim / README.md
Last active July 6, 2024 15:14
Sample README.md file

LIBRARY MANAGEMENT SYSTEM CLIENT

GitHub repo file count GitHub repo size GitHub GitHub commit activity GitHub contributors