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

gulp-angular-to-webpack-css-injection

v0.1.4

Published

Step in migration from gulp generated project (by 'gulp-angular') to webpack4. Injecting all **/*.css files in coresponding angularJs-entities. Adding `import "./filename.css"` in the very begginig of file (controller, module, component)

Downloads

25

Readme

gulp-angular-to-webpack-css-injection

N|Solid

Important notice

This module works, and sometimes it's helpful to have visiual representation of your css imports, according to your components. But it can be easily repalced by Webpack out of box functionality require.context. Following code in your entry point does the thing:

const context = require.context('./', true, /\.css/); // true - include subdirctories
context.keys().forEach(context);

However, this module can also handle this approach

Description:

If you (like many of us) used generator-gulp-angular to scaffold your application, and desperate willing to switch to Webpack builder, sooner or later you will bump in *.css imports trouble.

generator-gulp-angular creates next folder structure (simplified):

├── src                     
│   ├── app
│   │  ├── main
│   │  │    ├── main.controller.js
│   │  │    ├── main.html
│   │  │    ├── main.css
│   │  ├── index.config.js
│   │  ├── index.css
│   │  ├── index.module.js
│   │  ├── index.route.js
│   │  ├── index.run.js
│   ├── assets         
│   └── index.html
├── bower.json
├── package.json
└── gulpfile.js

And Gulp deals with your style files simply by concatenaiting them and injecting in index.html as <link rel="stylesheet" href="styles/app.css">. In Webpack you should handle styles by yourself, importing them where needed. In our project there are a lot of styles files that are in the directory with the corresponding component. It would take a long time to manually import styles into each file. Therefore, it was necessary to solve the optimization problem, for which the module was written.

Works in two ways: add imports to files or add file with require.context to your entry point

- NOTICE: First approach works only for next file namings style:
%name%.controller.js
%name%.component.js
%name%.module.js
etc.

You can provide your entities array, and pass them into module.

Installation

Module requires Node.js to run. Was tested with nodejs 8.11.1, and npm 5.6.0.

Install module as dev dependency via npm.

$ npm install --save-dev gulp-angular-to-webpack-css-injection

Require it in your Webpack configuration code or anywhere:

const cssInjection = require('gulp-angular-to-webpack-css-injection');

And run it: Add imports to files

cssInjection.useImports('src/app');

Function signature:

/*
* Public interface for injecting import css
* @param definedPath - string, your application folder, default 'src/app'
* @param angularJsEntitiesArray - array, default: ['component', 'controller', 'module']
*/
module.exports.useImports = (definedPath, angularJsEntitiesArray) => {
//code
};

Add import of require file to your entry point

cssInjection.useRequire('src/app/index.module.js', false);

Function signature:

/*
* Public interface for creating and adding require css file to your project
* @param entryPoint - string, entry point of your application
* @param removeImports - boolean - remove import css statements in folder if needed
* @param ignoreFiles - array - skip files while removing imports
*/
module.exports.useRequire = (entryPoint, removeImports = false) => {
//code
};

Use with caution: removeImports = true will remove all import '%name%.css'; and import "%name%.css"; from your source files. You can pass array of file names (or globs) to skip them while removing, like src/app/vendor.js. May be helpful if you are using extract-text-webpack-plugin. Since extract-text-webpack-plugin only merges text chunks, some CSS duplication may occur.

Result

Your source code changed from:

export class MainController {
  constructor ($state) {
    'ngInject';
  }
}

To:

import './main.css';
export class MainController {
  constructor ($state) {
    'ngInject';
  }
}

For future Webpack bundling flow.

Or, after using useRequire: styles.index.js created and imported to your entry point;

License

MIT