Michael J. Zoidl michaelzoidl

npm Users By Downloads (git.io/npm-top)

npm users sorted by the monthly downloads of their modules, for the range May 6, 2018 until Jun 6, 2018.

Metrics are calculated using top-npm-users.

#	User	Downloads

There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.

All other files should be in your own global gitignore file:

Create a file called .gitignore in your home directory and add any filepath patterns you want to ignore.
Tell git where your global gitignore file is.

Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute .config/git/ignore for .gitignore in your home directory, if you prefer.

	"use client"

	import * as React from "react"
	import { buttonVariants } from "@/components/ui/button"
	import { ScrollArea } from "@/components/ui/scroll-area"
	import { Select, SelectContent, SelectItem, SelectTrigger, SelectValue } from "@/components/ui/select"
	import { cn } from "@/lib/utils"
	import { ChevronLeft, ChevronRight } from "lucide-react"
	import { DayPicker, DropdownProps } from "react-day-picker"

	// Ignore those pesky styles
	require('ignore-styles');

	// Set up babel to do its thing... env for the latest toys, react-app for CRA
	require('babel-register')({
	ignore: /\/(build\|node_modules)\//,
	presets: ['env', 'react-app']
	});

	// Now that the nonsense is over... load up the server entry point

	#! /usr/bin/env node
	// I am ./bin/buildSitemap.js

	const path = require('path')
	const glob = require('glob')
	const fs = require('fs')

	const SITE_ROOT = process.env.SITE_ROOT \|\| 'https://www.actionherojs.com'
	const SOURCE = process.env.SOURCE \|\| path.join(__dirname, '..', 'pages', '/*/.js')
	const DESTINATION = process.env.DESTINATION \|\| path.join(__dirname, '..', 'static', 'sitemap.xml')

	/* HOC fundamentally is just a function that accepts a Component and returns a Component:
	(component) => {return componentOnSteroids; } or just component => componentOnSteroids;
	Let's assume we want to wrap our components in another component that is used for debugging purposes,
	it just wraps them in a DIV with "debug class on it".
	Below ComponentToDebug is a React component.
	*/

	//HOC using Class
	//it's a function that accepts ComponentToDebug and implicitly returns a Class
	let DebugComponent = ComponentToDebug => class extends Component {

	// NOTE: I previously suggested doing this through Grunt, but had plenty of problems with
	// my set up. Grunt did some weird things with scope, and I ended up using nodemon. This
	// setup is now using Gulp. It works exactly how I expect it to and is WAY more concise.
	var gulp = require('gulp'),
	spawn = require('child_process').spawn,
	node;

	/**
	* $ gulp server
	* description: launch the server. If there's a server already running, kill it.

	require('typescript-require')({nodeLib: true});
	require("./gulpfile.ts");

	console.reset = function () {
	return process.stdout.write('\033c');
	}

	@font-face {
	font-family: 'EntypoRegular';
	src: url('font/entypo.eot');
	src: url('font/entypo.eot?#iefix') format('embedded-opentype'),
	url('font/entypo.woff') format('woff'),
	url('font/entypo.ttf') format('truetype'),
	url('font/entypo.svg#EntypoRegular') format('svg');
	font-weight: normal;
	font-style: normal;
	}