typescript-starter
starter-workflows
Our great sponsors
typescript-starter | starter-workflows | |
---|---|---|
5 | 258 | |
1,775 | 8,421 | |
2.3% | 2.2% | |
4.7 | 8.3 | |
22 days ago | about 15 hours ago | |
TypeScript | TypeScript | |
- | 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-starter
-
5 steps to create a bare minimum NestJS app from scratch!
Let's say you want to create a new NestJS standard application from scratch but taking the full control of your dependencies, scripts and source code. Thus, you don't want to use the usual npx @nestjs/cli new command (which basically bootstraps the typescript starter project) since you wish a bare minimum app.
-
whoever created Nest.js he really likes complexity!
You don't need to use the Nest CLI if you don't want to. You can literally just create a index.ts file, use NestJS within it and run it with ts-node index.ts (though you gotta make sure you have the correct tsconfig.json)
-
Getting started with NestJS, Vite, and esbuild
Another option is to clone the starter repo from GitHub. Note that to install the JavaScript flavor of the starter project, we can clone this repo, but you’ll need Babel to compile vanilla JavaScript).
- CI/CD with a simple NestJS server
-
Seeding NestJs with Prisma And Faker
git clone https://github.com/nestjs/typescript-starter.git project cd project yarn yarn add -D prisma npx prisma init
starter-workflows
-
Most Useful CI/CD Tools for DevOps
GitHub Actions is a feature-rich CI/CD platform embedded within GitHub, enabling developers to automate, customize, and execute software development workflows directly in their repositories. An Action inside GitHub Actions is a discrete unit of automation that performs a specific task within a workflow. All the Actions are reusable, and there are many to choose from. You can even create your own reusable ones.
-
Awesome GitHub Action Workflows
actions/starter-workflows
-
Laravel code-quality tools
The real power of using PHP code-quality tools is when it’s added to your continuous integration process, which means it automatically checks the code every time someone makes a push or pull request to your project repo. In this section, we'll be looking at how to do just that. GitHub actions is available for free so we'll use it for demo purposes. Note that there are some limits to private repos, so set your test repo to public if you can.
-
Elevate Your GitHub README Game
You can even automate the running of this script — hence the directory name automation — to happen every time the data changes, using GitHub Actions.
-
GitHub Status Checks and Branch Protection Made Easy
# Based on https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml name: CI on: pull_request: branches: - main jobs: ci: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: lts/* cache: 'npm' - run: npm ci - run: npm run build --if-present - run: npm test
-
GitHub Actions for Perl Development
You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Perl Conference in Toronto last summer I gave a talk called “GitHub Actions for Perl Development” (here are the slides and the video).
-
How to Get Preview Environments for Every Pull Request
Preevy is designed to be easily run in CI/CD workflows, such as GH Actions, Circle CI and others.
-
CI using GitHub Actions
I set out to add further development and contribution tools to my ez-txt2html converter. Specifically, I wanted to introduce an initial Continuous Integration workflow. For this, I used the “Python Application” workflow template in Github Actions to create a CI testing workflow that builds a Py v3.12 environments, builds the project dependencies, runs Flake8 linting and Black formatting and then subsequently runs PyTest using the test suites I’ve written previously.
-
14 DevOps and SRE Tools for 2024: Your Ultimate Guide to Stay Ahead
GitHub Actions
-
GitHub Actions Workflow
To start, I turned to the starter-workflows repository, a valuable resource housing diverse YAML files for various project types. My project being in .NET, I checked out the dotnet.yml file to get insights into the setup process. Understanding the YAML syntax and keywords like on, push, jobs, and steps is crucial for crafting an effective workflow. In my case, I wanted to the workflow to trigger "on" any "pushes" on the main branch. The job describes the specific task which can be given a name, and steps outline the necessary steps to run the job.
What are some alternatives?
nest-keycloak-connect - keycloak-nodejs-connect module for Nest
argocd-image-updater - Automatic container image update for Argo CD
dotenv - A Ruby gem to load environment variables from `.env`.
CppCon2020 - Slides and other materials from CppCon 2020
typeorm - TypeORM module for Nest framework (node.js) 🍇
NewPipe - A libre lightweight streaming front-end for Android.
nest-next - Render Module to add Nextjs support for Nestjs
nnn - n³ The unorthodox terminal file manager
dotenv - Loads environment variables from .env for nodejs projects.
Real_Time_Image_Animation - The Project is real time application in opencv using first order model
node-koa-starter - Starter project for node js web applications. It uses typescript and koa.
react-native-dotenv - Load react native environment variables using import statements for multiple env files.