jeffjewiss / broccoli-postcss Goto Github PK
View Code? Open in Web Editor NEWπ³ Postcss compiler as a Broccoli filter.
License: MIT License
π³ Postcss compiler as a Broccoli filter.
License: MIT License
Branch | Build failing π¨ |
---|---|
Dependency | eslint-plugin-import |
Current Version | 2.3.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-import 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 10 commits.
44ca158
update utils changelog
a3728d7
bump eslint-module-utils to v2.1.0
3e29169
bump v2.4.0
ea9c92c
Merge pull request #737 from kevin940726/master
8f9b403
fix typos, enforce type of array of strings in allow option
95315e0
update CHANGELOG.md
28e1623
eslint-module-utils: filePath in parserOptions (#840)
2f690b4
update CI to build on Node 6+7 (#846)
7d41745
write doc, add two more tests
dedfb11
add allow glob for rule no-unassigned-import, fix #671
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
I have another request/proposal!
One thing that I've come across (rarely) is the need to configure a PostCSS plugin with information about the current directory of the files being operated on. Specifically, I've run into this with postcss-sprites
and the need to locate the sprites themselves. Brococli makes this a bit tough, since you don't actually know where the files are on disk anymore.
We solves this issue by allowing a plugin
to be a callback, that was threaded the output directory and the current file being processed. You can check out the code we've used here.
Would you be willing to consider a third type of plugin, a callback
, in addition to the two methods supported here? Again, I'll add the feature (and tests) if you're willing to accept a PR that added that feature.
Thanks!
Thank you for taking the time to open an issue!
For bug reports, please provide the version of broccoli-postcss
, and list of postcss plugins you are using.
This appears to be because autoprefixer 10 required postcss 8 and broccoli-postcss uses postcss 7.
Updating to latest postcss version using Broccoli is throwing a type error, tried with different approaches but none worked:
Using "broccoli-postcss": "6.1.0"
which uses "postcss": "8.1.4"
Same error using "broccoli-postcss-single": "5.0.2"
which also uses "postcss": "8.1.4"
My brocfile:
...
const postcss = require("broccoli-postcss");
...
export default ({env}) => {
...
const cssPlugins = {
plugins: [
{
module: postcssMixins
},
{
module: postcssMomentumScrolling
},
{
module: postcssPresetEnv,
options: {
stage: 0,
preserve: false,
}
},
]
};
...
postcss("css", {plugins: cssPlugins})
...
After adding the new
keyword it throws the following error:
Thanks for your broccoli plugin. I was struggling to get it to work, because I'm knew to broccoli and just copied and pasted the example and the build was always failing.
Turns out it's no longer cssnext
but postcss-cssnext
:)
I'll provide a pull request for the fix in the readme!
The from
/ to
paths passed to postcss
are relative. This causes filters that need to access other files in the tree, like postcss-inline-svg
, to fail to find the correct files. Rather than finding it in the tree, it will search the source files instead. This means that any processing on these files are lost, or that it fails to find the file since it would be generated / renamed during tree processing.
I suspect it can be fixed by prepending this.inputPath
/ this.outputPath
to the passed options.
Sorry I'm new with brocolli and also postcss
is there a way to set the destDir???
options.destDir = 'somoDir':
compileCSS('assets/styles/vendor/css', options);
Regards,
Mariano
wrong quotes in require(βcssnextβ);
Branch | Build failing π¨ |
---|---|
Dependency | mocha |
Current Version | 3.2.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 πͺ
Thanks to all our contributors, maintainers, sponsors, and users! β€οΈ
As highlights:
--inspect-brk
on command-line (@igwejk)semistandard
directly (@kt3k)The new version differs by 89 commits0.
fb1687e
:ship: Release v3.3.0
1943e02
Add Changelog for v3.3.0
861e968
Refactor literal play-icon hex code to a var
1d3c5bc
Fix typo in karma.conf.js
9bd9389
Fix spec paths in test HTML files
0a93024
Adds tests for loading reporters w/ relative/absolute paths (#2773)
73929ad
Comment special treatment of '+' in URL query parsing
e2c9514
Merge pull request #2769 from igwejk/support_inspect_break_in_opts
038c636
Support --inspect-brk
on command-line
b4ebabd
Merge pull request #2727 from lamby/reproducible-build
882347b
Please make the build reproducible.
a2fc76c
Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests
ed61cd0
cover .some() function in utils.js with tests
f42cbf4
Merge pull request #2701 from craigtaub/landingSpec
6065242
use stubbed symbol
There are 89 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 π΄
I've noticed that some fatal compilation errors occurring during postcss compilation are not being surfaced to the console
Branch | Build failing π¨ |
---|---|
Dependency | nyc |
Current Version | 10.2.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As nyc 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 4 commits ahead by 4, behind by 2.
55e826d
chore(release): 10.3.0
89dc7a6
chore: explicit update of istanbul dependnecies (#562)
1887d1c
feat: add support for --no-clean, to disable deleting raw coverage output (#558)
ff73b18
fix: source-maps were not being cached in the parent process when --all was being used (#556)
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 π΄
Looks like node 11 isn't supported.
yarn install v1.12.3
[1/5] π Validating package.json...
[2/5] π Resolving packages...
[3/5] π Fetching packages...
error [email protected]: The engine "node" is incompatible with this module. Expected version "^4.5 || ^6 || ^7 || ^8 || ^9 || ^10". Got "11.6.0"
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.```
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 π΄
You should check your code with PostCSS Runner Guidelines. It is mandatory for all PostCSS runner. Fill free to ask any question about this rules.
It is now version 2.0, see gabrielgrant/broccoli-less-single#33 for how an upgrade was done.
Branch | Build failing π¨ |
---|---|
Dependency | coveralls |
Current Version | 2.12.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As coveralls 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 4 commits .
2821200
version bump
ef7e811
Parse commit from packed refs if not available in refs dir. (#163)
e476964
Merge pull request #162 from evanjbowling/patch-1
63a7f92
Update README.md
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | coveralls |
Current Version | 2.13.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As coveralls 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 1 commits0.
b9032a1
better Jenkins detection
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 π΄
Branch | Build failing π¨ |
---|---|
Dependency | async |
Current Version | 2.1.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As async 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 | async |
Current Version | 2.3.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As async 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 | nyc |
Current Version | 10.3.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As nyc 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 2 commits0.
e062a86
chore(release): 10.3.2
213206f
fix: we should not create a cache folder if cache is false (#567)
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 π΄
Branch | Build failing π¨ |
---|---|
Dependency | nyc |
Current Version | 10.1.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As nyc 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 6 commits .
455619f
chore(release): 10.2.0
95cc09a
feat: upgrade to version of yargs with extend support (#541)
43535f9
chore: explicit update of istanbuljs dependencies (#535)
98ebdff
feat: allow babel cache to be enabled (#517)
50adde4
feat: exclude the coverage/ folder by default π (#502)
6a59834
chore(package): update tap to version 10.0.0 (#507)
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Hi!
It would be great if this plugin had an option to run as a filter, applying postcss to every .css
file in the input trees, without specifying inputFile
/ outputFile
.
I'm a little new to using Broccoli outside of Ember-CLI. Can you expand your README example to describe where in a typical broccoli setup your example would fit? Just placing your example into a Brocfile is yielding non-descript errors. I'm sure I'm missing a basic step, but I imagine others may benefit from a little extra boilerplate for getting started.
I'm getting this error when I attempt to install using Yarn 1.5.1 on a Node v10 system.
PR incoming
[3/5] π Fetching packages...
error [email protected]: The engine "node" is incompatible with this module. Expected version "^4.5 || ^6 || ^7 || ^8 || ^9".
error An unexpected error occurred: "Found incompatible module".
Hello
Currently broccoli-postcss support plugins
option as an Array
.
But postCSS standard config for webpack postcss-loader use an Object
.
https://github.com/michael-ciniawsky/postcss-load-config#postcssrcjs-or-postcssconfigjs
So if we respect postCSS documentation about the config file, it fail with broccoli-postcss
- stack: TypeError: opts.plugins.forEach is not a function
at PostcssFilter.processString (β¦/node_modules/broccoli-postcss/index.js:54:16)
at resolve (β¦/node_modules/broccoli-postcss/node_modules/broccoli-persistent-filter/lib/strategies/default.js:18:19)
at initializePromise (β¦/node_modules/broccoli-postcss/node_modules/rsvp/dist/rsvp.js:523:7)
at new Promise (β¦/node_modules/broccoli-postcss/node_modules/rsvp/dist/rsvp.js:1017:35)
at Object.processString (β¦/node_modules/broccoli-postcss/node_modules/broccoli-persistent-filter/lib/strategies/default.js:17:18)
at Processor.processString (β¦/node_modules/broccoli-postcss/node_modules/broccoli-persistent-filter/lib/processor.js:24:27)
at resolve (β¦/node_modules/broccoli-postcss/node_modules/broccoli-persistent-filter/index.js:433:16)
at initializePromise (β¦/node_modules/broccoli-postcss/node_modules/rsvp/dist/rsvp.js:523:7)
at new Promise (β¦/node_modules/broccoli-postcss/node_modules/rsvp/dist/rsvp.js:1017:35)
at invoke (β¦/node_modules/broccoli-postcss/node_modules/broccoli-persistent-filter/index.js:432:10)
Maybe we should use postcss-load-config
module
I was wondering if there was a reason that this plugin doesn't support an array of plugins as well as the modules/options
objects that it currently accepts. For example, being able to specify this:
{
plugins: [
require('autoprefixer')(options)
]
}
instead of the modules/options separately
{
plugins: [
{
module: require('autoprefixer'),
options
}
]
}
I ask because I'd like to be able to use this package within ember-css-modules
, but would want to allow the postprocess
plugins to use the same interface that the before
and after
plugins there do. I'm happy to make a PR if you're amenable to having both methods be supported.
Since I know that the options for each plugin are merged with some global options, I would propose that plugins handed their options directly would just opt out of this behavior altogether, which seems like reasonable behavior unless there's some reason that that can't be done.
I'm using this plugin within an ember application to process an individual folder, and this is how I did:
const themeStyles = new Funnel('themes', { destDir: 'assets/themes' });
const themeTree = PostCSSCompiler(themeStyles, {
plugins: [...],
broswers: [...]
});
return new MergeTrees([app.toTree(), themeTree]);
It works pretty well actually, but I have a little problem with postcss-import
plugin. Let's say I have two style files as:
/* main.css */
@import './module.css';
/* module.css */
.test {
/* rules */
}
Now, if I edit the module.css
file, ember-cli will recompile it, but main.css
will not, so I had to save both of them every time. Is there any way to improve this?
Branch | Build failing π¨ |
---|---|
Dependency | eslint |
Current Version | 3.17.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint 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 26 commits .
ca1d478
3.18.0
3688024
Build: package.json and changelog update for 3.18.0
85f74ca
Fix: broken code path of direct nested loops (fixes #8248) (#8274)
a61c359
Fix: Ignore hidden folders when resolving globs (fixes #8259) (#8270)
6f05546
Chore: convert StubModuleResolver in config tests to ES6 class (#8265)
0c0fc31
Fix: false positive of no-extra-parens about spread and sequense (#8275)
e104973
Docs: remove self-reference in no-restricted-syntax docs (#8277)
23eca51
Update: Add allowTaggedTemplates to no-unused-expressions (fixes #7632) (#8253)
f9ede3f
Upgrade: doctrine to 2.0.0 (#8269)
1b678a6
New: allow rules to listen for AST selectors (fixes #5407) (#7833)
63ca0c5
Chore: use precalculated counts in stylish formatter (#8251)
7d1af86
Update: fix false negative of no-useless-escape in template literal tags (#8238)
47c3171
Fix: typo in console.error (#8258)
e74ed6d
Chore: convert Traverser to ES6 class (refs #7849) (#8232)
13eead9
Fix: sort-vars crash on mixed destructuring declarations (#8245)
There are 26 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 π΄
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.