mistakster / postcss-pipeline-webpack-plugin Goto Github PK
View Code? Open in Web Editor NEWA webpack plugin to process generated assets with PostCSS pipeline
A webpack plugin to process generated assets with PostCSS pipeline
Branch | Build failing π¨ |
---|---|
Dependency | css-loader |
Current Version | 0.28.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As css-loader is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | postcss |
Current Version | 6.0.14 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
postcss is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
from
option on process().then()
call.There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
This plugin is great replacement for https://github.com/NMFR/optimize-css-assets-webpack-plugin (which does not support Webpack v5) and its option cssProcessor
with postcss instead of default cssnano
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.travis.yml
package.json
files, so that was left aloneIf youβre interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.
Greenkeeper has checked the engines
key in any package.json
file, the .nvmrc
file, and the .travis.yml
file, if present.
engines
was only updated if it defined a single version, not a range..nvmrc
was updated to Node.js 10.travis.yml
was only changed if there was a root-level node_js
that didnβt already include Node.js 10, such as node
or lts/*
. In this case, the new version was appended to the list. We didnβt touch job or matrix configurations because these tend to be quite specific and complex, and itβs difficult to infer what the intentions were.For many simpler .travis.yml
configurations, this PR should suffice as-is, but depending on what youβre doing it may require additional work or may not be applicable at all. Weβre also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, Iβm a humble robot and wonβt feel rejected π€
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
7.0.24
to 7.0.25
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
postcss is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Can I change fullname of critical file? Not only suffix
I want set name for critical as critical.[contenthash:12].css
Name for prod files as app.395ff6e90875.critical.css
is very strange
contenthash from filename relation to app.css not critical.css
When app.css will be changed the hash will also be changed but content of critical part maybe not
6.0.2
to 6.1.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
options
parameter (@plroebuck).jsonc
extension (@sstephant)These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:
this.skip()
in "before each" hooks (@juergba)--allow-uncaught
for uncaught exceptions thrown inside hooks (@givanse)and some regressions:
Suite
cloning by copying root
property (@fatso83)The new version differs by 28 commits.
f4fc95a
Release v6.1.0
bd29dbd
update CHANGELOG for v6.1.0 [ci skip]
aaf2b72
Use cwd-relative pathname to load config file (#3829)
b079d24
upgrade deps as per npm audit fix; closes #3854
e87c689
Deprecate this.skip() for "after all" hooks (#3719)
81cfa90
Copy Suite property "root" when cloning; closes #3847 (#3848)
8aa2fc4
Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
586bf78
Update JS-YAML to address security issue (#3845)
d1024a3
Update doc examples "tests.html" (#3811)
1d570e0
Delete "/docs/example/chai.js"
ade8b90
runner.js: "self.test" undefined in Browser (#3835)
0098147
Replace findup-sync with find-up for faster startup (#3830)
d5ba121
Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
a3089ad
update package-lock
75430ec
Upgrade yargs-parser dependency to avoid loading 2 copies of yargs
There are 28 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | mocha |
Current Version | 5.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 15 commits.
09ce746
Release v5.0.1
70027b6
update changelog for v5.0.1 [ci skip]
44aae9f
add working wallaby config
412cf27
[Update] license year
b7377b3
rename help-wanted to "help wanted" in stale.yml
d975a6a
fix memory leak when run in v8; closes #3119
3509029
update .gitignore to only ignore root mocha.js [ci skip]
b57f623
fix: When using --delay, .only() no longer works. Issue #1838
cd74322
Slight copy update on docs for test directory
f687d2b
update docs for the glob
14fc030
Add all supported wallaby editors
2e7e4c0
rename "common-mistake" label to "faq"
bca57f4
clarify docs on html, xunit and 3p reporters; closes #1906
2fe2d01
Revert "fix travis "before script" script"
c0ac1b9
fix travis "before script" script
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
In my case critical styles not removed from main bundle of style
I need add PostCssPipelineWebpackPlugin
with criticalSplit
and output: rest
?
Branch | Build failing π¨ |
---|---|
Dependency | extract-text-webpack-plugin |
Current Version | 2.1.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As extract-text-webpack-plugin is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
The new version differs by 13 commits.
0271b39
chore(release): 2.1.1
e595417
fix: don't extract from common async chunks (#508)
a8ae003
chore(package): fix broken links && update devDependencies (#531)
c3cb091
fix(loader): rm unnecessary this.cacheable
(caching) (#530)
eaa5236
docs: rm RELEASE.md
(#532)
671e35e
chore(package): update webpack-sources
v0.1.0...1.0.1 (#526)
dfeb347
fix: validation schema (schema-utils
) (#527)
d0e88d0
docs(README): add lead-in description (#517)
58dd5d3
fix: add a not null check for the content property before throwing error (#404)
6c50d8e
Update README.md (#469)
c63dc04
docs(README): clarify to set allChunks option when using CommonsChunkPlugin (#476)
c40dc64
chore(package): reduce package size (#482)
a284f3a
docs(README): fix options table formatting (#478)
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
The version 4.1.1 is requiring a processor
key on the config object. That's ok, however the SemVer prohibit patch releases of introduce breaking changes.
When I downgrade it to 4.1.0 the error go away.
I just replaced pipeline
config key name for processor
and it started to work once again.
{omitted}/node_modules/webpack-cli/bin/cli.js:231
throw err;
^
Error: You must provide a PostCSS processor instance
at new PostCssPipelineWebpackPlugin ({omitted}/node_modules/postcss-pipeline-webpack-plugin/lib/postcss-pipeline-webpack-plugin.js:24:11)
at Object.module.exports.getConfig ({omitted}/src/tools/webpack/postcss/pipeline.js:16:9)
at generateConfig ({omitted}/src/tools/webpack/postcss/postcss.js:20:19)
at Object.module.exports.getConfig ({omitted}/src/tools/webpack/postcss/postcss.js:36:10)
at externalCssExtraction ({omitted}/src/tools/webpack/plugins.js:11:17)
at getPlugins ({omitted}/src/tools/webpack/plugins.js:57:4)
at standa...
Branch | Build failing π¨ |
---|---|
Dependency | mocha |
Current Version | 3.3.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As mocha is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.
This week's highlights:
allowUncaught
added to commandline as --allow-uncaught
(and bugfixed)--no-warnings
and --trace-warnings
flags (@sonicdoe)The new version differs by 9 commits0.
7554b31
Add Changelog for v3.4.0
9f7f7ed
Add --trace-warnings
flag
92561c8
Add --no-warnings
flag
ceee976
lint test/integration/fixtures/simple-reporter.js
dcfc094
Revert "use semistandard
directly"
93392dd
no special case for macOS running Karma locally
4d1d91d
--allow-uncaught cli option
fb1e083
fix allowUncaught in browser
4ed3fc5
Add license report and scan status
false
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
7.0.9
to 7.0.10
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
postcss is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
0.8.0
to 0.8.1
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
mini-css-extract-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 7 commits.
054532a
chore(release): 0.8.1
2f72e1a
fix: support ES module syntax (#472)
c7eda97
refactor: only output when any chunk is fulfilled (#468)
357d073
fix: improve warning of conflict order (#465)
50434b5
refactor: loader's code (#448)
159ce3b
refactor: fix typo (#440)
0bacfac
fix(options): use filename mutated after instantiation (#430)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | webpack |
Current Version | 4.17.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 7 commits.
ee27d36
4.17.3
4430524
Merge pull request #7966 from webpack/refactor-remove-webpack-command-from-clis
b717aad
Show only webpack-cli in the list
c5eab67
Merge pull request #8001 from webpack/bugfix/exit-code
943aa6b
Fix exit code when multiple CLIs are installed
691cc94
Spelling
898462d
refactor: remove webpack-command
from CLIs
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
βοΈ Greenkeeperβs updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing π¨ |
---|---|
Dependency | webpack |
Current Version | 4.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
version
property to webpack exportsimport()
with CJS now gives correct exportsThe new version differs by 8 commits.
5044762
4.0.1
7fd5c6f
Merge pull request #6585 from webpack/bugfix/bailout-messages
8e592bf
Merge pull request #6575 from nveenjain/addVersion
e7aba18
fix incorrect optimization bailout messages
9f9c3d1
Merge pull request #6583 from webpack/bugfix/import-cjs
8bf1574
CJS fake namespace object contains exports now
d50fa68
add newlines
05174ae
Added version to webpack's export property
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Hey,
This is exactly what I'm looking for :).
I'm using this in my Webpack Config and it is generating the critical file and also the map, but when I add in the comments where I want the scss to be extracted nothing seems to enter that file.
Would you like to me post the webpack.config.js here?
Thanks, Jake.
Branch | Build failing π¨ |
---|---|
Dependency | webpack |
Current Version | 2.5.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As webpack is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
The new version differs by 24 commits.
859b8cd
updated examples
af05c14
2.6.0
74afac5
Merge pull request #4881 from webpack/bugfix/destructing
cd6d086
fix missing pattern walk
231a638
fix parsing issue with patterns
272c105
support destructing on assignment
6bd3a82
Merge pull request #4902 from bdwain/master
04f2622
require a newer version of uglify that fixes a bug with regexp
6d24f0d
Merge pull request #4882 from kdnk/fix-typo
7e4d659
CI
60f154f
archieved β> achieved
95400b8
Merge pull request #4865 from PeterTeng/peter/fix-typo-in-examples
d5d0428
Merge pull request #4880 from webpack/ci/appveyor-yarn
8ee65f1
Workaround for weird yarn link behavior
b59e179
'it it' => 'in in'
There are 24 commits in total.
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
If I use the build hash as a query param (e.g. app.css?123456
) by defining [name].css?[contenthash]
in the webpack configuration, postcss-pipeline isn't able to find the output file. If I remove the hash, the build is working as expected.
4.41.2
to 4.41.3
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 5 commits.
df9f3eb
4.41.3
fe71d68
Merge pull request #10010 from webpack/funding
b396d96
Merge pull request #10123 from pustovalov/webpack-4-serialize
29b2bdd
Update terser-webpack-plugin to ^1.4.3
bedb566
chore: funding
field
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Hi,
I am using this plugin in order to extract the critical css and generate the rest css files, but when I am processing the assets with the webpack-assets-manifest plugin, these files don't appear in the assets. The only place I could find references to the new files is in the manifest.stats
but it is not sufficient for me to use. Why don't they appear in the assets array?
3.3.0
to 3.3.1
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
css-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 10 commits.
cbca64d
chore(release): 3.3.1
3b12c87
refactor: code (#1017)
c80c39f
fix: handling urls in @import (#1016)
30a9269
fix: handling escaped urls (#1015)
e091d27
fix: reduce count of require
(#1014)
60c65e0
fix: characters as URL escapes in url (#1013)
8e8ab18
fix: handling string urls with backslash and newline (#1012)
b59c4f2
test: special characters in file name (#1011)
b119d02
fix: handling unquoted syntax url with escaped characters (#1010)
880344b
refactor: code (#1009)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
4.35.3
to 4.36.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
append
option now supports the default placeholders in addition to [url]
"..."
when overriding options.The new version differs by 42 commits.
95d21bb
4.36.0
aa1216c
Merge pull request #9422 from webpack/feature/dot-dot-dot-merge
b3ec775
improve merging of resolve and parsing options
53a5ae2
Merge pull request #9419 from vankop/remove-valid-jsdoc-rule
ab75240
Merge pull request #9413 from webpack/dependabot/npm_and_yarn/ajv-6.10.2
0bdabf4
Merge pull request #9418 from webpack/dependabot/npm_and_yarn/eslint-plugin-jsdoc-15.5.2
f207cdc
remove valid jsdoc rule in favour of eslint-plugin-jsdoc
31333a6
chore(deps-dev): bump eslint-plugin-jsdoc from 15.3.9 to 15.5.2
036adf0
Merge pull request #9417 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.8.0
37d4480
Merge pull request #9411 from webpack/dependabot/npm_and_yarn/simple-git-1.121.0
ce2a183
chore(deps-dev): bump eslint-plugin-jest from 22.7.2 to 22.8.0
0beeb7e
Merge pull request #9391 from vankop/create-hash-typescript
bf1a24a
#9391 resolve super call discussion
bd7d95b
#9391 resolve discussions, AbstractMethodError
4190638
chore(deps): bump ajv from 6.10.1 to 6.10.2
There are 42 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | postcss-critical-split |
Current Version | 2.5.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As postcss-critical-split is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
4.26.1
to 4.27.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
getResolve
method to create their own resolver function with custom optionsexport * from
The new version differs by 12 commits.
f47bf8b
4.27.0
a67ffcd
Merge pull request #8452 from webpack/feature/resolveWithOptions
96f625c
Merge pull request #8457 from webpack/bugfix/rebuild-provided-exports
56feccc
convert test case to normal function for node.js 6 support
2f4296e
fix a bug which causes incorrect providedExports for cached modules
f944002
Merge pull request #8451 from webpack/bugfix/split-chunks
162da1c
add getResolve method to loader context
3b46b48
enforce doesn't affect minSize for maxSize
72a8a1f
Merge pull request #8440 from Connormiha/oprimize-chunk-can-be-integrated
537d3e4
Cache hasRunstime in chunk
e3e8a68
Merge pull request #8405 from xiaoxiaojx/fix-function-plugin-apply
70b9a1b
fix parameter missing when plugin type is a funtion
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Is it possible to choose not to put a dot and put a dat xxx-critical.css.
Also I use mini-css-extract-plugin,
new MiniCssExtractPlugin({ filename: 'styles-[hash:8].css' }),
Is there a was to make the -critical
before the hash? (it's kinda like #41 )
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.