npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@daniellacosse/generator-typescript

v0.0.5

Published

develop typescript at scale with a full suite of helpful tools

Downloads

21

Readme

@daniellacosse/generator-typescript

npm version

installation

before you get started, you'll need to install homebrew: [ mac | linux ]

brew install yarn
yarn global add yo @daniellacosse/generator-typescript

creating a project

feel free to add this to your ~/.bash_profile or just run the commands manually:

dts() {
  read MY_PROJECT_NAME

  # the terminal will wait for you to type in the name of your project. please use `pascal-case`

  mkdir $MY_PROJECT_NAME
  cd $MY_PROJECT_NAME

  # the magic part 🧙‍♂️
  yo @daniellacosse/typescript
  
  # run `make` as a smoke test
  make
}

this will generate the boilerplate. now the hard part - setting up github and circleci

pushing to github

first, click the + in the top right.

step 1

NOTE ⚠️: the name of your repository must match the name of your project/project folder

now, you can push your project:

git push -u origin master

refresh the page, and you should see it


next, there are a couple configuration steps to take care of in github that we unfortunately have to do manually. first, it's preferred to only allow squashed commits

this is important because it keeps the commit chain short, the history good, and increases the chance that each commit on the main branch is atomic and transportable

go to Settings:

step 2

and then scroll down to select these options:

step 3

secondly, we should set some branch restrictions on master. this is to encourage good behavior and best practices.

scroll back up and click the Branches pill in the sidebar:

step 4

you should see an option to create a rule:

step 5

your new rule should default to master. at minimum, we should enforce our circleci checks. this means that, in order to be able to merge our code, that code will need to pass whatever tests we select here:

step 6

if you don't see anything, skip to the authorizing circleci section and then come back here.

NOTE ⚠️: unfortunately, you shouldn't enforce these restrictions for administrators. circleci needs to be able to push to the branch directly for this setup to work. to be pure, with a paid github account you can create a special group and put the circleci bot in it, though you'll have to set that up yourself

authorizing circleci

almost done. we just need to get circleci running. make sure you have an account.

at circleci.com, go to Add Projects

step 7

then Set Up project

step 8

we've already got a config, so you can just scroll down to Start building

step 9

then, in the Jobs tab you'll need to click on the ⚙️ icon next to your project name and scroll down to the Checkout SSH Keys tab:

step 10

here you can add your 🔑 user keys to circleci. circleci will then have access it needs to do everything for you.


step 11

that's it! if you have any questions, please create an issue.

License

MIT © Daniel LaCosse