typescript-action
typescript-eslint
typescript-action | typescript-eslint | |
---|---|---|
29 | 123 | |
1,799 | 14,663 | |
3.2% | 1.2% | |
9.2 | 9.9 | |
3 days ago | 4 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
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.
typescript-action
-
Hashnode Blog GitHub Action - fetch and display the latest blogs in a nice format
While learning about GitHub Actions, I came across the GitHub Actions Org, and they have a bunch of templates for building custom GitHub actions. So, I started searching for a template that has TypeScript support, ensuring type safety to write bug-free code. I found the typescript-action template that includes support for tests, linter, versioning, and more.
-
Dynamically importing a downloaded file in a TypeScript GitHub action.
This is the template I used for my TypeScript action https://github.com/actions/typescript-action
-
Develop, test, and deploy your extensions for all popular CIs from a single codebase
I found the GitHub actions documentation easier to read than Azure, so I would recommend starting writing and testing your extensions on GitHub by using the official template actions/typescript-action. The mentioned template provides a good starting point; I won't repeat the steps here. Play with it, write some simple stuff, and then return here for the next steps.
-
Speeding up GitHub Actions with npm cache
GitHub maintain a set of repos called actions. One of which is called cache.
-
AdaGPT: My Learnings While Building a GitHub Action
To get started quickly with a JavaScript action, I recommend using the official templates from GitHub for JavaScript and TypeScript.
-
Rust is not hard! Part 1: GitHub Actions
On the TypeScript side, setup was much easier. There was already a template from GitHub that took care of the basics. Most of the time spent here was updating dependencies and getting my editor to play nicely with itβ18 minutes, about 10% of the total.
- CICD pipelines written in Typescript
- Unpopular opinion: CI/CD engines are an awful idea
-
Creating GitHub Actions for community engagement
Now that you know how to create your own GitHub Actions, why not give it a try? Head to the GitHub Marketplace and start exploring the existing Actions, or create your own and share it with the community. With GitHub Actions, the possibilities are endless, so start building and see what you can accomplish
-
How to Debug Tests in the CI Pipeline
Your build most likely fails because your tests fail. Most CI pipelines today, like Jenkins, Circleci, GitLab, TeamCity, Bamboo, and GitHub Actions, are configured to automatically cause the build process to fail when tests fail.
typescript-eslint
-
Mastering Type-Safe JSON Serialization in TypeScript
Typescript-eslint can assist in this task. This tool helps identify all instances of unsafe any usage. Specifically, all usages of JSON.parse can be found and it can be ensured that the received data's format is checked. More about getting rid of the any type in a codebase can be read in the article Making TypeScript Truly "Strongly Typed".
-
Oxlint β written in Rust β 50-100 Times Faster than ESLint
> Only lint files that have changed? How hard that is?
Quite hard, especially since type-aware rules from e.g. https://typescript-eslint.io/ mean that changing the type of a variable in file A can break your code in file B, even if file B hasn't changed.
-
How to Do a TypeScript Conversion: an opinionated take on gradual conversions
The article only touches this: when converting to TypeScript, `any` is useful, but in the end you don't want this type in your codebase - so don't forget to use typescript-eslint [0] and turn on those no-unsafe-* rules which guard against `any` leaking into your code.
[0] https://github.com/typescript-eslint/typescript-eslint
- How do I add additional rules to my typescript-eslint settings?
- What's the best config for typescript-eslint?
- How do you add angular-eslint to your typescript-eslint config?
- What's the best typescript-eslint config?
-
The Best ESLint Rules for React Projects
By convention, React components should be named in PascalCase. @typescript-eslint has the config we need, and though we can't specifically target React components, we can target variables (and set some other conventions while we're at it):
- Open source public fund experiment - One and a half years update
- Never touch those //ts-ignores
What are some alternatives?
codeql-action - Actions for running CodeQL analysis
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
ncc - Compile a Node.js project into a single file. Supports TypeScript, binary addons, dynamic requires.
angular-eslint - :sparkles: Monorepo for all the tooling related to using ESLint with Angular
get-changed-files - Get all of the files changed/modified in a pull request or push's commits.
ts-standard - Typescript style guide, linter, and formatter using StandardJS
sticky-pull-request-comment - create comment on pull request, if exists update that comment.
zod - TypeScript-first schema validation with static type inference
publish-unit-test-result-action - GitHub Action to publish unit test results on GitHub
node-clinic - Clinic.js diagnoses your Node.js performance issues
vercel-action - This action make a deployment with github actions instead of Vercel builder.
ts-node - TypeScript execution and REPL for node.js