jeffjewiss / broccoli-postcss Goto Github PK

View Code? Open in Web Editor NEW

30.0 30.0 18.0 3.18 MB

🌳 Postcss compiler as a Broccoli filter.

License: MIT License

CSS 1.59% JavaScript 98.41%

broccoli broccoli-plugin postcss postcss-plugins

broccoli-postcss's People

Contributors

Stargazers

Watchers

Forkers

thedeeno mmun kbalyasnikov topaxi dehuszar chriseppstein clickbox humanelement mike-north kketch briansipple synnr-skip alexlafroscia lougreenwood radium-io ryuran nlfurniss spruce

broccoli-postcss's Issues

An in-range update of mocha is breaking the build 🚨

Version 3.3.0 of mocha just got published.

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 💪

Status Details

- ❌ **bitHound - Dependencies** 2 failing dependencies. [Details](https://www.bithound.io/github/jeffjewiss/broccoli-postcss/7c51a4bd04d343b4c3ef52fac66da70b016099dc/dependencies/npm#filter-failing-dep),- ❌ **bitHound - Code** 1 failing file. [Details](https://www.bithound.io/github/jeffjewiss/broccoli-postcss/7c51a4bd04d343b4c3ef52fac66da70b016099dc/files#filter-failing-file),- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/jeffjewiss/broccoli-postcss/builds/225140394),- ✅ **coverage/coveralls** First build on greenkeeper/mocha-3.3.0 at 96.97% [Details](https://coveralls.io/builds/11209034)

Release Notes

coverave

Thanks to all our contributors, maintainers, sponsors, and users! ❤️

As highlights:

We've got coverage now!
Testing is looking less flaky \o/.
No more nitpicking about "mocha.js" build on PRs.

🎉 Enhancements

#2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
#2769: Support --inspect-brk on command-line (@igwejk)

🐛 Fixes

#2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)

🔍 Coverage

#2672: Add coverage for node tests (@c089, @Munter)
#2680: Increase tests coverage for base reporter (@epallerols)
#2690: Increase tests coverage for doc reporter (@craigtaub)
#2701: Increase tests coverage for landing, min, tap and list reporters (@craigtaub)
#2691: Increase tests coverage for spec + dot reporters (@craigtaub)
#2698: Increase tests coverage for xunit reporter (@craigtaub)
#2699: Increase tests coverage for json-stream, markdown and progress reporters (@craigtaub)
#2703: Cover .some() function in utils.js with tests (@seppevs)
#2773: Add tests for loading reporters w/ relative/absolute paths (@sul4bh)

🔩 Other

Remove bin/.eslintrc; ensure execs are linted (@boneskull)
#2542: Expand CONTRIBUTING.md (@boneskull)
#2660: Double timeouts on integration tests (@Munter)
#2653: Update copyright year ([@Scottkao85], @Munter)
#2621: Update dependencies to enable Greenkeeper (@boneskull, @greenkeeper)
#2625: Use trusty container in travis-ci; use "artifacts" addon (@boneskull)
#2670: doc(CONTRIBUTING): fix link to org members (@coderbyheart)
Add Mocha propaganda to README.md (@boneskull)
#2470: Avoid test flake in "delay" test (@boneskull)
#2675: Limit browser concurrency on sauce (@boneskull)
#2669: Use temporary test-only build of mocha.js for browsers tests (@Munter)
Fix "projects" link in README.md (@boneskull)
#2678: Chore(Saucelabs): test on IE9, IE10 and IE11 (@coderbyheart)
#2648: Use semistandard directly (@kt3k)
#2727: Make the build reproducible (@lamby)

Commits

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.3.2 of nyc just got published.

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 💪

Status Details

❌ bitHound - Dependencies 1 failing dependency. Details,- ❌ bitHound - Code 1 failing file. Details,- ✅ coverage/coveralls First build on greenkeeper/nyc-10.3.2 at 96.97% Details,- ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

Commits

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.4.0 of eslint-plugin-import just got published.

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 💪

Status Details

✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/eslint-plugin-import-2.4.0 at 100.0% Details
❌ bitHound - Code Error analyzing branch. Details
❌ bitHound - Dependencies Error analyzing branch. Details

Commits

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Support for node 11

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.```

An in-range update of coveralls is breaking the build 🚨

Version 2.13.1 of coveralls just got published.

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 💪

Status Details

- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/jeffjewiss/broccoli-postcss/builds/226594114),- ✅ **coverage/coveralls** First build on greenkeeper/coveralls-2.13.1 at 96.97% [Details](https://coveralls.io/builds/11279313),- ❌ **bitHound - Dependencies** 3 failing dependencies. [Details](https://www.bithound.io/github/jeffjewiss/broccoli-postcss/a36c022b5ddbc19d093c01eaec76fcb6aee06b52/dependencies/npm#filter-failing-dep),- ❌ **bitHound - Code** 1 failing file. [Details](https://www.bithound.io/github/jeffjewiss/broccoli-postcss/a36c022b5ddbc19d093c01eaec76fcb6aee06b52/files#filter-failing-file)

Commits

The new version differs by 1 commits0.

b9032a1 better Jenkins detection

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Dest dir?

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

An in-range update of nyc is breaking the build 🚨

Version 10.2.0 of nyc just got published.

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 💪

Status Details

✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/nyc-10.2.0 at 96.97% Details
❌ bitHound - Dependencies 1 failing dependency. Details
❌ bitHound - Code 1 failing file. Details

Commits

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.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Recompile while imported style file has changed?

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?

An in-range update of nyc is breaking the build 🚨

Version 10.3.0 of nyc just got published.

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 💪

Status Details

- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/jeffjewiss/broccoli-postcss/builds/227079581?utm_source=github_status&utm_medium=notification),- ✅ **coverage/coveralls** First build on greenkeeper/nyc-10.3.0 at 96.97% [Details](https://coveralls.io/builds/11301067),- ❌ **bitHound - Dependencies** 3 failing dependencies. [Details](https://www.bithound.io/github/jeffjewiss/broccoli-postcss/b6daa3e7742475d507f89bfcbe1347b812b425bf/dependencies/npm#filter-failing-dep),- ❌ **bitHound - Code** 1 failing file. [Details](https://www.bithound.io/github/jeffjewiss/broccoli-postcss/b6daa3e7742475d507f89bfcbe1347b812b425bf/files#filter-failing-file)

Commits

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of async is breaking the build 🚨

Version 2.4.0 of async just got published.

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 💪

Status Details

- ❌ **bitHound - Code** Error analyzing branch. [Details](https://www.bithound.io/github/jeffjewiss/broccoli-postcss/greenkeeper%2Fasync-2.4.0),- ❌ **bitHound - Dependencies** Error analyzing branch. [Details](https://www.bithound.io/github/jeffjewiss/broccoli-postcss/greenkeeper%2Fasync-2.4.0),- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/jeffjewiss/broccoli-postcss/builds/227250779?utm_source=github_status&utm_medium=notification),- ✅ **coverage/coveralls** First build on greenkeeper/async-2.4.0 at 96.97% [Details](https://coveralls.io/builds/11305742)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

The engine "node" is incompatible with this module

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".

Callbacks as plugins

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!

Running as a filter

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.

Typo in README.md

wrong quotes in require(‘cssnext’);

Support postcss.config.js standard format

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

Doesn't work with autoprefixer 10

This appears to be because autoprefixer 10 required postcss 8 and broccoli-postcss uses postcss 7.

An in-range update of coveralls is breaking the build 🚨

Version 2.13.0 of coveralls just got published.

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.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ bitHound - Code 1 failing file. Details
❌ bitHound - Dependencies 1 failing dependency. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/coveralls-2.13.0 at 96.97% Details

Commits

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.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Allowing an array of plugins instead of objects

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.

How does you example fit into a traditional Broccoli config

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.

PostCSS Runner Guidelines

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.

Support for nodejs 12.x?

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.

Fix example in the readme so the build won't fail

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!

Processing issue

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.

An in-range update of async is breaking the build 🚨

Version 2.2.0 of async just got published.

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 💪

Status Details

❌ bitHound - Dependencies 1 failing dependency. Details
❌ bitHound - Code 1 failing file. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/async-2.2.0 at 96.97% Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

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 💪

Status Details

✅ bitHound - Code No failing files. Details,- ✅ bitHound - Dependencies No failing dependencies. Details,- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v3.4.0

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)
warning-related Node flags

🎉 Enhancements

#2793, #2697: add --allowUncaught to Node.js (@lrowe)
#2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

#2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

#2778: Add license report and scan status (@xizhao)
#2794: no special case for macOS running Karma locally (@boneskull)
#2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Errors are not being surfaced to the console

I've noticed that some fatal compilation errors occurring during postcss compilation are not being surfaced to the console

An in-range update of eslint is breaking the build 🚨

Version 3.18.0 of eslint just got published.

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 💪

Status Details

❌ bitHound - Code 1 failing file. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ coverage/coveralls First build on greenkeeper/eslint-3.18.0 at 96.97% Details

Release Notes

v3.18.0

85f74ca Fix: broken code path of direct nested loops (fixes #8248) (#8274) (Toru Nagashima)
a61c359 Fix: Ignore hidden folders when resolving globs (fixes #8259) (#8270) (Ian VanSchooten)
6f05546 Chore: convert StubModuleResolver in config tests to ES6 class (#8265) (Teddy Katz)
0c0fc31 Fix: false positive of no-extra-parens about spread and sequense (#8275) (Toru Nagashima)
e104973 Docs: remove self-reference in no-restricted-syntax docs (#8277) (Vitor Balocco)
23eca51 Update: Add allowTaggedTemplates to no-unused-expressions (fixes #7632) (#8253) (Kevin Partington)
f9ede3f Upgrade: doctrine to 2.0.0 (#8269) (alberto)
1b678a6 New: allow rules to listen for AST selectors (fixes #5407) (#7833) (Teddy Katz)
63ca0c5 Chore: use precalculated counts in stylish formatter (#8251) (alberto)
47c3171 Fix: typo in console.error (#8258) (Jan Peer Stöcklmair)
e74ed6d Chore: convert Traverser to ES6 class (refs #7849) (#8232) (Teddy Katz)
13eead9 Fix: sort-vars crash on mixed destructuring declarations (#8245) (Teddy Katz)
133f489 Fix: func-name-matching crash on destructuring assignment to functions (#8247) (Teddy Katz)
a34b9c4 Fix: func-name-matching crash on non-string literal computed keys (#8246) (Teddy Katz)
7276e6d Docs: remove unneeded semicolons in arrow-parens.md (#8249) (Dmitry Gershun)
8c40a25 Upgrade: concat-stream known to be vulnerable prior 1.5.2 (#8228) (Samuel)
149c055 Upgrade: mock-fs to v4.2.0 (fixes #8194) (#8243) (Teddy Katz)
a83bff9 Build: remove unneeded json config in demo (fixes #8237) (#8242) (alberto)
df12137 Docs: fix typos (#8235) (Gyandeep Singh)
b5e9788 Chore: rename no-extra-parens methods (#8225) (Vitor Balocco)
7f8afe6 Update: no-extra-parens overlooked spread and superClass (fixes #8175) (#8209) (Toru Nagashima)
ce6ff56 Docs: set recommended true for no-global-assign (fixes #8215) (#8218) (BinYi LIU)
5b5c236 Fix: wrong comment when module not found in config (fixes #8192) (#8196) (alberto)

Commits

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.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Update broccoli-caching-writer

It is now version 2.0, see gabrielgrant/broccoli-less-single#33 for how an upgrade was done.

TypeError: Class constructors cannot be invoked without 'new'

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:

jeffjewiss / broccoli-postcss Goto Github PK

broccoli-postcss's People

Contributors

Stargazers

Watchers

Forkers

broccoli-postcss's Issues

Version 3.3.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔍 Coverage

🔩 Other

Version 10.3.2 of nyc just got published.

Version 2.4.0 of eslint-plugin-import just got published.

Version 2.13.1 of coveralls just got published.

Version 10.2.0 of nyc just got published.

Version 10.3.0 of nyc just got published.

Version 2.4.0 of async just got published.

Version 2.13.0 of coveralls just got published.

Version 2.2.0 of async just got published.

Version 3.4.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔩 Other

Version 3.18.0 of eslint just got published.

Recommend Projects

Recommend Topics

Recommend Org