Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
dev-init
Advanced tools
Readme
This project will get you started and automate a whole bunch of little things you need to do to every new project in order to work sanely with a team or accept contributions from other members of the open-source community. Since there are so many little steps, they take time and you always end up forgetting something and needing to make a bunch of tweaks later on. You should skip all of that, and just use this module to get up and running quickly.
I appreciate your enthusiasm.
npm install -g dev-init
Easy:
mkdir my-cool-lib
cd my-cool-lib
dev-init
git init
The regular git init
command is run for the module, to create all the necessary git bits.
.gitignore
A default .gitignore
file is used, suitable for NodeJS module and application development on macOS, Windows, and Linux. If you already have one of these files (perhaps you want to run this module on an existing repo), the values from this list will be merged into your existing file.
.gitattributes
A default .gitattributes
file is used, to standardize file checkouts across macOS, Windows, and Linux. This will ensure things like linting will never be broken on operating systems that you might not be using, but other members on your team are. If this file already exists, this will be skipped by default.
.brackets.json
Kiril approves of Brackets. So a configuration file is created to correctly set up Brackets. If you already have this file, the settings will be merged into your existing file.
There is an option here to select your preferred linter:
dev-init --linter ESLint
You can define as many linters as you would like to use:
dev-init --linter ESLint --linter JSHint --linter JSCS
You can also configure the number of spaces to use for indentation, although I strongly encourage you to stick to 4.
dev-init --spaces 2
.editorconfig
Kiril also approves of other IDEs. An .editorconfig
file will be created to configure a whole plethora of other IDEs. If your favorite IDE does not support it natively, there is probably a plugin for it. If you already have this file, the settings will be merged into your existing file.
Like with .brackets.json
, spaces are configurable.
dev-init --spaces 2
README.md
An empty readme file will be created, to get you started and remind you that writing a readme is important. If a README already exists, this will be skipped by default.
I'd like to think it is. I did a great job writing it. And, just so you know, if there is a merge error, your existing files will be safe. However, if you don't trust me, there is a flag for that.
dev-init --safe
With this flag, existing files will be left untouched.
Yeah. Not all files can be merged at this time. For those, I will respect your existing settings and leave them alone (until I can figure out a good way to merge them, anyway).
If you do want to use the files from this module, however, there is a flag for that too:
dev-init --force
This flag will replace all of the skipped files with the ones generated by this module. Files that are usually merged will still be merged.
Well, this is your lucky day, because you have options:
dev-init --include list of tasks
You can use the --include
flag, followed by a space-separated list of task names, as a whitelist for which tasks to run.
dev-init --exclude list of tasks
You can use the --exclude
flag, followed by a space-separated list of task names, as a blacklist for tasks to skip.
You can also combine these, but they apply on top of one another (i.e. the exclude list will exclude tasks that were explicitly included in the include list).
dev-init select
You can use the select
command to enter an interactrive menu, where you can visually select the tasks to run.
That's easy too:
dev-init list
And if that is too much typing:
dev-init ls
That's not really a question, but it is also okay. Not everyone has to make the correct choices. You can still use this project though, to configure and enforce the settings you do prefer. Feel free to clone it and make all the changes you would like to the files in the fixtures
folder.
You can set it up in your dev environment as such:
git clone git@github.com:catdad/dev-init.git
cd dev-init
npm install
npm link
Now you can make changes and use the dev-init
cli command with your local version.
FAQs
Initialize a new project with Kiril-approved settings
The npm package dev-init receives a total of 8 weekly downloads. As such, dev-init popularity was classified as not popular.
We found that dev-init demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.