npmpackage.info

Gathering detailed insights and metrics for laravel-mix-postcss-config

laravel-mix-postcss-config - 1.4.0 | npmpackage.info

laravel-mix-postcss-config

A Laravel-mix plugin to add the postcss-loader to the default mix webpack.config.js file.

1.4.0

MIT

JavaScript

6.38 kB

2.7

Installations

npm install laravel-mix-postcss-config

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

12.19.0

NPM Version

6.14.8 Pull Requests

Open

3

Total

16

Closed

7

Merged

6

Issues

Open

1

Total

3

Closed

2

Releases

Laravel-mix version 5 and move to GitHub actions

v1.4.0

Updated on Nov 22, 2020

View All 1 releases

Languages

JavaScript

JavaScript (100%)

Developer

yazeedobaid

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

6 Stars

24 Commits

4 Branches

2 Contributors

Updated on Apr 13, 2022

Maintainers

View All 2 Contributors

Package Meta Information

Latest Version

1.4.0

Package Id

laravel-mix-postcss-config@1.4.0

Unpacked Size

6.38 kB

Size

2.78 kB

File Count

NPM Version

6.14.8

Node Version

12.19.0

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Peer Dependencies

laravel-mix

Dev Dependencies

eslint eslint-config-prettier eslint-plugin-prettier postcss-loader prettier

laravel-mix-postcss-config

GitHub npm npm

A Laravel-mix plugin to add the postcss-loader loader with its configuration file to the default mix webpack.config.js file in a fluent way.

1mix.js('resources/js/app.js', 'public/js')
2    .postCss('resources/css/app.css', 'public/css')
3    .postCssConfig();

Introduction

Laravel mix has a great and fluent api to define the build steps for an application. Mix has supprt for defining postcss plugins through the postCss api. Defining these plugins along with their options in mix's config file will make the file large and difficult to read.

postcss-loader provide a way to define postcss plugins in a separate config file (postcss.config.js). This plugin extends laravel-mix api and add a method to include the loader with its config file in the build process.

Install

Install using npm:

$ npm install laravel-mix-postcss-config --save-dev

Usage

Require the pulgin in your laravel-mix config file and call the extension method on mix.

1const mix = require('laravel-mix');
2require('laravel-mix-postcss-config');
3
4mix.js('resources/js/app.js', 'public/js')
5    .postCss('resources/css/app.css', 'public/css')    
6    .postCssConfig();

The above call will merge the postcss-loader loader to mix's generated webpack config rules with the default loader configuration options. If you wish to change the default loader options you can pass them in the call:

1const mix = require('laravel-mix');
2require('laravel-mix-postcss-config');
3
4mix.js('resources/js/app.js', 'public/js')
5    .postCss('resources/css/app.css', 'public/css')    
6    .postCssConfig({ /* postcss-loader options */ });

You can find a list of possible postcss-loader loader options in the loader github repository

License

The MIT License (MIT). Please see License File for more information.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.7

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More