bases VS gitignore

We will install ready-to-use Typescript base configurations instead of starting from scratch. In this article, we will use Typescript base configurations for node version 20. If you are using a different version of node, visit the tsconfig bases docs to find out what you need. You can also create a Typescript configuration file with settings that work for you.

This Visual Studio Code extension simplifies the process of selecting and applying TypeScript configuration files (`tsconfig.json`) from the https://github.com/tsconfig/bases repository. With this extension, you can effortlessly browse through available configuration

Steal from this repo: https://github.com/tsconfig/bases/blob/main/bases/next.json

I personally am a big advocate for writing the least amount of tsconfig possible, and the tsconfig/bases package serves as a great source for getting tsconfig templates.

Possibly depends on your tsconfig. We use the recommended base configs from here https://github.com/tsconfig/bases

A tsconfig.json preset that ensures type safety;

The same configuration is also available for other nodejs versions like 14 and 12.

After installing, we also need to set up a basic tsconfig.json file for how we want tsc to behave with our app. We will use one of the recommended tsconfig files here: https://github.com/tsconfig/bases#centralized-recommendations-for-tsconfig-bases. This contains a list of community recommended configs depending on your app type. We’re using Node 16 and want to be extremely strict on the first pass to clean up any bad code habits and enforce some consistency. We’ll use the one located: https://github.com/tsconfig/bases/blob/main/bases/node16-strictest.combined.json.

You'll need @typescript-eslint/parser to get it working with eslint, then I would add @typescript-eslint/recommended as a plugin, then add prettier-eslint for formatting. What's more important is having a really good tsconfig file, I would recommend extending something from https://github.com/tsconfig/bases

The above configuration file extends the base configuration provided by the TypeScript team for Node.js v16. Additional options or overrides may be included through the compilerOptions property. It also specifies that all the files in the src directory should be included in the program, but everything in the node_modules directory is skipped entirely. Both the include and exclude properties support glob patterns.

In conclusion, the Gitignore repository stands as a testament to the power of collective knowledge and collaboration in software development. By providing a centralized repository of .gitignore templates, it empowers developers to streamline their workflow, maintain cleaner repositories, and focus on what they do best – writing exceptional code. As the software development landscape continues to evolve, the significance of .gitignore templates as indispensable tools for developers is set to endure.

The challenge here was actually from my #48in28 Exercism participation, where I am pretty familiar the standard layout for some repositories since I am familiar with tooling and language, working with new languages does not come with the same familiarity, so I found it made sense to use canonical definitions, hence the use of github/gitignore.

Add .env to your .gitignore file to prevent it from being committed. Here's an example file with it already added. You may also use dotenv for advanced configuration and it will automatically load environment variables from a .env file into process.env.

Here you can find ready-made .gitignore templates for various technologies and languages such as Python, Java, Kotlin, Go, and many others: https://github.com/github/gitignore/tree/main.

You could also use this git ignore template. Create you .gitignore and add the contents from that file in.

I've only used free Unity with GitHub or GitLab, professionally and reaching back into internships. One recommendation would be to use a slightly longer .gitignore than the default, like this one.

Virtual Environments are a feature that has been part of python itself since version 3.3. It allows you to isolate both a python version and any packages you install with it. Every python project I develop with uses a virtual environment for such isolation purposes. Now I generally like to create these virtual environments inside the target project's directory so I know exactly what it's tied to. If you use GitHub's python gitignore file naming the virtual environment folder as venv or .venv will ensure it doesn't get committed (which you don't want). So I'll make a new project folder and create a virtual environment inside of it:

Especially considering the GitHub .gitignore template for Node only ignores .env.local, not .local.env: https://github.com/github/gitignore/blob/main/Node.gitignore...

# Get latest from https://github.com/github/gitignore/blob/main/Unity.gitignore