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

required-loader-cp

v1.3.17

Published

Require a whole directory of trees in bulk

Downloads

25

Readme

webpack-require-loader-cp

Loader receives a file tree from a template and import them with the necessary parameters settings.

It can be used to import any kind of files. You can use it in javascript files or style files. Works great with ng-include and ng-cache when developing angular applications.

Help author (donate)

Support Webpack 1.x and Webpack 2.x

Install

npm i required-loader-cp --save-dev

Simple Usage

Add in your code comment:

/* input string in code */
//@require "./modules/**/index.js"

/* output */
require('./modules/one/index.js');
require('./modules/two/index.js');
require('./modules/three/index.js');

Usage with import props

Add in your code comment:

//@require "./modules/**/index.js?import[]=angular,go={hello:'world'}"
  • If the import parameters are set in the webpack.config.js file and in @require comment, they both will be imported into the included files

More examples

//@require "./modules/**/index.js?import[]=angular,import[]=$=jquery,go={hello:'world'}"

//@require "./**/!(index|config|run)*"

//@require "./**/*"

//@require "./**/*.html"

Usage in CSS/SCSS/STYL/LESS files

/* input string in style file */
@require "./**/!(app|bootstrap).css";
@require "./**/*.less";
@require "./**/*.scss";
@require "./**/*.styl";
/* output */
@import 'style/header.css';
@import 'style/layout.css';
@import 'style/menus.css';

webpack.config.js

JS loader

{
test: /\.js$/,
  loader: 'required?import[]=angular',
}

OR

loaders: ["ng-annotate","babel","required?import[]=angular,params={ip:'0.0.0.0'}"]

CSS loaders

{
test: /\.css$/,
  loader: 'required',
}

OR

loader: ExtractTextPlugin.extract("style","css?sourceMap!postcss!required")

Params

Param | Description ------------|------- import | import modules in required scripts params | import params in required scripts. It can be any variable name. Params in loader === var params = {ip:'0.0.0.0'} in file witch require

The following characters have special magic meaning when used in a path portion:

  • * Matches 0 or more characters in a single path portion
  • ? Matches 1 character
  • [...] Matches a range of characters, similar to a RegExp range. If the first character of the range is ! or ^ then it matches any character not in the range.
  • !(pattern|pattern|pattern) Matches anything that does not match any of the patterns provided.
  • ?(pattern|pattern|pattern) Matches zero or one occurrence of the patterns provided.
  • +(pattern|pattern|pattern) Matches one or more occurrences of the patterns provided.
  • *(a|b|c) Matches zero or more occurrences of the patterns provided
  • @(pattern|pat*|pat?erN) Matches exactly one of the patterns provided

If you find a mistake, don't be lazy, write. Thank you.

Pull request welcome