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

@intouchg/tarot

v0.0.2

Published

Easy custom Webpack configs for SCSS and JS

Downloads

8

Readme

@intouchg/tarot

Easy custom Webpack configs for SCSS and JS

Features

  • babel-loader
  • webpack-bundle-analyzer
  • CSS / SCSS entry files
  • SCSS with PostCSS autoprefixer and media query sorting
  • SCSS $env variable based on Webpack mode

Usage

  1. Set up your webpack.config.js using tarot:
// webpack.config.js
const { build } = require('@intouchg/tarot')

module.exports = build({
	// Entry keys are used as the filename of the bundled output,
	// with appropriate file extension automatically added, and
	// are relative to the output directory.
	// Entry values are used as the filepath of the entry file,
	// and are relative to the source directory.
	entries: {
		bundle: 'index.js',
		styles: 'index.scss',
		['js/bundle-' + new Date().toISOString()]: 'index.js',
	},

	// Options
	source: 'src2', // Source directory, default 'src'
	output: 'dist2', // Output directory, default 'dist'
	https: true, // Enable HTTPS, default false
	cors: true, // Enable CORS, default false
	copy: [ // Copy static assets, default []
		{
			from: 'assets', // Relative to the source directory
			to: 'other' // Relative to the output directory
		}
	],

	// Note: Webpack `context` is assumed to be process.cwd()
})
  1. Use webpack-cli and arguments to build:
webpack serve
webpack --mode development
webpack --analyze

Prior Art