angular-eslint
Angular
angular-eslint | Angular | |
---|---|---|
22 | 699 | |
1,563 | 94,541 | |
0.6% | 0.3% | |
9.4 | 10.0 | |
5 days ago | 5 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
angular-eslint
-
Lint rule for self-closing tags in Angular
Until I recently discovered that angular-eslint had added a new lint rule in v16.2 called prefer-self-closing-tags that can be used to enforce this syntax partially or throughout a project.
- How to create service call to get users
-
Angular 16 Unveiled: Discover the Top 7 Features
We are also using angular-eslint which now supports 16.0.3 so that was painless.
-
Angular Universal SSR ESLint rules?
Along the lines of Angular ESLint, are there any packages that provide ESLint rules around writing SSR friendly code?
-
npx storybook init does not work properly? It installs react and react-dom, also the components are full of errors?! Am I doing something wrong?
{ "root": true, "ignorePatterns": ["projects/**/*"], "rules": { "prettier/prettier": [ "error", { "endOfLine": "auto" } ] }, "overrides": [ { // TODO: find a way to apply rules on all files ending with .ts except for files ending with .stories.ts "files": ["*.ts"], "extends": [ "eslint:recommended", "plugin:@typescript-eslint/recommended", "plugin:@angular-eslint/recommended", "plugin:@angular-eslint/template/process-inline-templates", "plugin:prettier/recommended" ], "rules": { // https://github.com/angular-eslint/angular-eslint/tree/main/packages/eslint-plugin/docs/rules "@angular-eslint/directive-selector": [ "error", { "type": "attribute", "prefix": "hv", "style": "camelCase" } ], "@angular-eslint/component-selector": [ "error", { "type": "element", "prefix": "hv", "style": "kebab-case" } ], // https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin/docs/rules "@typescript-eslint/member-ordering": "error", "@typescript-eslint/naming-convention": "error", // https://eslint.org/docs/latest/rules/ "default-case": "error", "default-case-last": "error" } }, { "files": ["*.html"], "extends": [ "plugin:@angular-eslint/template/recommended", "plugin:prettier/recommended" ], "rules": { // https://github.com/angular-eslint/angular-eslint/tree/main/packages/eslint-plugin-template/docs/rules "@angular-eslint/template/no-duplicate-attributes": ["error"], "@angular-eslint/template/attributes-order": ["error"], "@angular-eslint/template/no-call-expression": [ "error" ], "@angular-eslint/template/accessibility-elements-content": [ "error", { "allowList": [ "ariaLabel" ] } ], "@angular-eslint/template/accessibility-valid-aria": [ "error" ] } }, { "files": ["*.stories.@(ts|mjs|cjs)"], "extends": ["plugin:storybook/recommended"] // https://github.com/storybookjs/eslint-plugin-storybook/tree/main/docs/rules // "rules": {} } ] }
-
Personal Angular Best Practices
I don't think it's crazy, but these things improved my code quality a lot: * Use Prettier, an opinionated code formatter. It formats your code, no configuration, no fights with your colleagues. * Use eslint and SonarLint. They help you find bugs before you even commit your code. * Try to achieve a very high code coverage. Not every line needs to be covered, but I personally feel better if I've got 90+% coverage. It's not that hard once you include it in your coding-DNA. * Setup your IDE to properly debug your code. Don't do console.log(), use debugger; statements or real conditional breakpoints. Nothing sucks more than not being able to find out what your code really does. * Learn the ES6 and later features. Many developers tend to code in old ways (as they are used to), but JavaScript can do so much more these days. You'll save a lot of time and effort applying these new features. Start with Arrow Functions, followed by Rest and Spread operator, Property Shorthand and * Destructuring . Also note that there are some awesome new datastructures like Map and Set. * Learn TypeScript and keep yourself up to date. There are so many anti-patterns (never ever use any) that degregate your fancy, strictly typed highlevel code to buggy ES-code. It also helps a lot to reduce DRY and boilerplate. * Learn rxjs and use it on a daily base. Angular itself is really reactive as most Angular services return Observables that can be further processed with rxjs. Once your mind made the switch, you won't really use regular Events and/or loops anymore. But be aware of how to properly test your rxjs pipelines. * If you are integrating a remote API, I have very good experiences with OpenAPI and it's code generator for Angular. You will get ready-to-use interfaces and services just from an OpenAPI specification (which you get as a gift for many of the modern backend frameworks). Saves a lot of time and boilerplate code and removes the need to test and debug API-layer code. Your build will break as soon as the API introduces a breaking change, which is exactly what you want (it's too late if your app breaks on production)
-
Angular ESLint Rules for Keyboard Accessibility
If you're not already using Angular ESLint, you can add it to an Angular project by running the schematic:
-
Adding the ESLint to an Angular application
ng add @angular-eslint/schematics βΉ Using package manager: npm β Found compatible package version: @angular-eslint/[email protected]. β Package information loaded. The package @angular-eslint/[email protected] will be installed and executed. Would you like to proceed? Yes β Packages successfully installed. All @angular-eslint dependencies have been successfully installed π Please see https://github.com/angular-eslint/angular-eslint for how to add ESLint configuration to your project. We detected that you have a single project in your workspace and no existing linter wired up, so we are configuring ESLint for you automatically. Please see https://github.com/angular-eslint/angular-eslint for more information. CREATE .eslintrc.json (984 bytes) UPDATE package.json (1511 bytes) UPDATE angular.json (3447 bytes) β Packages installed successfully.
-
Getting started with Husky and Lint-staged for pre-commit hooks
We need two tools to get the job done. The first tool that we need is a pre-commit tool that runs for every git-commit action: Husky. The second tool that is needed is lint-staged, which will run specified scripts on matching staged files. Aside from these tools, we need a code repository with actual linting tools. We will be using an Angular project as an example with the Angular ESLint and Prettier pre-configured.
-
Angular: Migrate from TSLint to ESLint
You can find all necessary tools and information to simplify the migration of existing Angular projects to ESLint at the GitHub Repo Angular ESLint.
Angular
-
Angular Signals, Reactive Context, and Dynamic Dependency Tracking
/** * https://github.com/angular/angular/blob/75a186e321cb417685b2f13e9961906fc0aed36c/packages/core/src/render3/reactivity/untracked.ts#L15 * * packages/core/src/render3/reactivity/untracked.ts * **/ export function untracked(nonReactiveReadsFn: () => T): T { const prevConsumer = setActiveConsumer(null); try { return nonReactiveReadsFn(); } finally { setActiveConsumer(prevConsumer); } }
- Episode 24/15: Wiz behind the curtain, Copilot in VSCode
-
Always unsubscribe. No exceptions. Debate closed.
source: https://github.com/angular/angular/issues/46542
-
Angular Signals: Best Practices
Besides the dangers, mentioned by Angular docs (infinite loops, change detection errors), there is another thing, that might be quite nasty: effects are executed in a reactive context, and any code you call in effect, will be executed in a reactive context. If that code reads some signals, they will be added as dependencies to your effect. Here Alex Rickabaugh explains the details.
-
Understanding control flow syntax in Angular 17
In June 2023, the Angular team raised a new RFC to implement control flow syntaxes within Angular. They gave the following rationale for introducing control flow syntax:
- Episode 24/09: Testing without TestBed, SSR & Hydration
-
Preparing our Code for Zoneless Angular
For scheduling, I use awesome code I found in the Angular source code.
-
β° Itβs time to talk about Import Map, Micro Frontend, and Nx Monorepo
Just to give you more context, I led the migration of several AngularJS applications to the newer Angular Framework. My client finally decided to make that move following the AngularJS deprecation announcement (stay up to date please π)οΈ.
-
Conventional commit specification
Link β angular/CONTRIBUTING.md
-
Angular Control Flow: the complete guide
Angular v17 was released some months ago with a ton of new features, a brand new logo and the new blog angular.dev.
What are some alternatives?
typescript-eslint - :sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
Next.js - The React Framework
rushstack - Monorepo for tools developed by the Rush Stack community
qwik - Instant-loading web apps, without effort
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
SvelteKit - web development, streamlined
angular-eslint - Application example built with Angular 14 and adding the ESLint using @angular-eslint/schematics library.
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
prettier - Prettier is an opinionated code formatter.
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
eslint-plugin-storybook - πOfficial ESLint plugin for Storybook
lit - Lit is a simple library for building fast, lightweight web components.