jeffjewiss / ember-cli-postcss Goto Github PK

Version 2.12.0 of ember-cli just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli 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 💪

Your Greenkeeper Bot 🌴

/*jshint node:true*/
/* global require, module */
var EmberApp = require('ember-cli/lib/broccoli/ember-app');
var cssnext = require('postcss-cssnext');


module.exports = function(defaults) {
  var app = new EmberApp(defaults, {
    // Add options here
    postcssOptions: {
      plugins: [ { module: cssnext } ]
    }
  });


  return app.toTree();
};

not sure why this isn't compiling. anything i'm doing wrong?

Hi, thanks for this addon.

I'm trying to use this addon for sass compilation instead of ember-cli-sass. I have it working in a simple project. Now I'm trying to get it working in a simple addon.

I have an addon.scss in the addon/styles and an app.scss in the tests/dummy/app/styles. I also have the following postCssOptions block in both the index.js and ember-cli-build.js:

        postcssOptions: {
            compile: {
                extension: 'scss',
                enabled: true,
                parser: require('postcss-scss'),
                plugins: [
                    {
                        module: require('@csstools/postcss-sass')
                    }
                ]
            },
            filter: {
                enabled: false
            }
        }

If I try to serve the dummy app I get the following error:

Build Error (PostcssCompiler)

File to read not found or unreadable: /Users/markhaugen/Code/proj/f-sass/sass-addon/tmp/postcss_compiler-input_base_path-OOj6IiXF.tmp/app/styles/app.scss#sass


Stack Trace and Error Report: /var/folders/6x/nxm5z03d58v31b94qy10n1rc0000gp/T/error.dump.ecb0e9e92bff17a4ada2f2ac0e4758e8.log

I looked in the log and it doesn't have much other than file not found. If I look at that location there is an app.scss file there (though it doesn't have the hash sass bit). Do you know what I'm missing?

Thanks!

Version 4.5.0 of loader.js just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As loader.js 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 💪

Your Greenkeeper Bot 🌴

Version 2.2.0 of eslint-plugin-standard just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-standard 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 💪

Your Greenkeeper Bot 🌴

Hi, thanks for this addon.

Is it possible to specify include and exclude on the plugin level on filter?

Thanks !

I see in e268966 that support for Node 4 was dropped which prevents this package from being installed via yarn when using Node 4.

Node 4 is still an active LTS version, is there something specific in this addon that is incompatible? At Ghost we follow Node's LTS schedule so we need to still need to support v4, I was a bit surprised when a patch version update killed our Travis builds.

Version 3.0.1 of ember-resolver just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-resolver 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 💪

Your Greenkeeper Bot 🌴

When postcss-bem-linter and postcss-log-warnings are installed (with postcss-log-warnings as the last object in the Brocfile.js configuration) the build is succesful, but no warnings are logged. Even though I'm importing a component that should result in a warning:

app/styles/app.css

@import "./components/mycomponent.css";

app/styles/components/mycomponent.css

/** @define MyComponent */

/* this should result in a warning: */
.WrongName {}

I'm using postcss-import to process @import rules, could it be that this is causing problems? I believe postcss-bem-linter expects separate files, with the @define rule on the first line (to trigger linting). Since ember-cli-postcss looks for app.css or {app-name}.css, and only processes that, could that be the reason linting isn't triggered?

If so, can this be fixed from ember-cli-postcss, and how?

I'm working on a blueprint that will set a consuming app's ember-cli-blueprint.js with a SASS-compatible post-css plugin stack. There has been a lot of excitement around postcss in the ember community, but SASS has by far the most adoption. This will give people an easy way to switch over cleanly, and then add more plugins from there.

When using this addon together with e.g. 'autoprefixer', you currently configure autoprefixer like this:

plugins: [
  {
    module: autoprefixer,
    options: {
      browsers: ['last 2 versions', 'ie > 9', 'ios >= 8', '> 5%']
    }
]

Following the new possibilities as outlined here: http://rwjblue.com/2017/04/21/ember-cli-targets/, you can now have a config/targets.js file like this:

module.exports = {
  browsers: ['> 5%']
};

It would be great if we could use that config if no browsers are set directly for autoprefixer (and possibly other plugins).

Version 4.2.0 of loader.js just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As loader.js 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 💪

Your Greenkeeper Bot 🌴

As far as I can tell, this addon does not allow for any options, other than the plugins array, to be passed to broccoli-postcss. In turn broccoli-postcss does not seem to accept options for configuring sourcemap generation (but from what I can tell, it should generate a separate sourcemap by default. In the generated css, ember-cli-postcss does add a comment referring to a sourcemap:

/*# sourceMappingURL={app-name}.css.map */

But the sourcemap itself is never generated. Should ember-cli-postcss be generating a sourcemap currently, or is that still under development?

I'm trying to use this plugin but I can´t. I'm sure there is something I'm missing, but I prefer to share it, because maybe there are more people having same problem.

What I'm trying to do is very simple: I have a css of a component (inside styles folder, I realized pods are not working for the moment) and an import statement in my app.css

File: my-ember-app/app/styles/app.css

@import './templates/components/widgets/external/analytics-widget.css';

File: my-ember-app/app/styles/templates/components/widgets/external/analytics-widget.css

.analytics-widget-container{
  animation-name: example-animation;
  animation-duration: 2s;
  animation-iteration-count: infinite;
}

@keyframes example-animation {
  0% {background-color: red;}
  33% {background-color: green;}
  66% {background-color: blue;}
  100% {background-color: red;}
}

Then, when I start ember server or directly make a build, the css is not bundled inside assets/my-ember-app.css, because import hasn't been resolved, so it's looking for my-ember-app/app/styles/templates/components/widgets/external/analytics-widget.css in runtime.

Am I doing something wrong? I understood plugin should bundle all my referenced css by imports starting at app.css.

Version 5.2.3 of ember-cli-babel just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli-babel 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 💪

Your Greenkeeper Bot 🌴

Version 6.4.1 of ember-cli-babel just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli-babel 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 💪

Your Greenkeeper Bot 🌴

Version 3.0.3 of ember-cli-eslint just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli-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 💪

Your Greenkeeper Bot 🌴

Version 4.3.0 of loader.js just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As loader.js 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 💪

Your Greenkeeper Bot 🌴

I was not able to use this addon for addons see https://pixelhandler.com/posts/developing-ember-addons-next-generation-css-with-postcss

Do you think this addon can support building styles for addons ?

Version 2.0.2 of ember-cli-htmlbars just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli-htmlbars 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 💪

Your Greenkeeper Bot 🌴

Not sure what's up here. I've used this plugin in the past. You can see below a successful run of ember s and then I install this plugin, and then ember s fails.

ember-cli: 2.13.3
node: 6.9.5
os: darwin x64

sclark:whitebox-dashboard sean$ ember s
Looks like you have a different program called watchman.
Visit https://ember-cli.com/user-guide/#watchman for more info.
Livereload server on http://localhost:49153
'instrument' is imported from external module 'ember-data/-debug' but never used

Build successful (7110ms) – Serving on http://localhost:4200/



Slowest Nodes (totalTime => 5% )              | Total (avg)         
----------------------------------------------+---------------------
Babel (16)                                    | 5689ms (355 ms)     
Rollup (1)                                    | 514ms               

cleaning up...
sclark:whitebox-dashboard sean$ ember install ember-cli-postcss
Yarn: Installed ember-cli-postcss
Installed addon package.
sclark:whitebox-dashboard sean$ ember s
Looks like you have a different program called watchman.
Visit https://ember-cli.com/user-guide/#watchman for more info.
Livereload server on http://localhost:49153
'instrument' is imported from external module 'ember-data/-debug' but never used
The Broccoli Plugin: [BroccoliMergeTrees] failed with:
Error: Build Canceled: Broccoli Builder ran into an error with PostcssCompiler plugin. 💥
    at new BroccoliBuildError (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/broccoli-builder/lib/broccoli-build-error.js:40:9)
    at /Applications/MAMP/htdocs/whitebox-dashboard/node_modules/broccoli-builder/lib/builder.js:168:19
    at tryCatch (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/rsvp/dist/rsvp.js:539:12)
    at invokeCallback (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/rsvp/dist/rsvp.js:554:13)
    at publish (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/rsvp/dist/rsvp.js:522:7)
    at publishRejection (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/rsvp/dist/rsvp.js:457:3)
    at flush (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/rsvp/dist/rsvp.js:2414:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

The broccoli plugin was instantiated at: 
    at BroccoliMergeTrees.Plugin (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/broccoli-plugin/index.js:7:31)
    at new BroccoliMergeTrees (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/ember-cli-postcss/node_modules/broccoli-merge-trees/index.js:16:10)
    at BroccoliMergeTrees (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/ember-cli-postcss/node_modules/broccoli-merge-trees/index.js:10:53)
    at PostcssPlugin.toTree (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/ember-cli-postcss/index.js:36:10)
    at /Applications/MAMP/htdocs/whitebox-dashboard/node_modules/ember-cli-preprocess-registry/preprocessors.js:180:26
    at Array.forEach (native)
    at processPlugins (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/ember-cli-preprocess-registry/preprocessors.js:178:11)
    at module.exports.preprocessCss (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/ember-cli-preprocess-registry/preprocessors.js:148:10)
    at EmberApp.styles (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/ember-cli/lib/broccoli/ember-app.js:1336:32)
    at EmberApp.toArray (/Applications/MAMP/htdocs/whitebox-dashboard/node_modules/ember-cli/lib/broccoli/ember-app.js:1675:12)

Is it possible to add a parser like https://github.com/postcss/postcss-scss with the ember-cli-postcss in the postcssOptions? If so, what would that look like? Thanks

By default, source maps are disabled in ember build --environment=production. But using ember-cli-postcss, source maps are included in app.css.

Hey, can you bump the broccoli-postcss version dependency to 3.5.3 which I added a PR for yesterday?

Cheers :)

Version 2.12.2 of ember-cli just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli 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 💪

Your Greenkeeper Bot 🌴

Version 4.1.0 of loader.js just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As loader.js 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 💪

Your Greenkeeper Bot 🌴

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

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 💪

Your Greenkeeper Bot 🌴

After installing I am getting this error WARNING: The baseURLandrootURL settings should not be used at the same time.. Believe this has to do when ember moved to rootURL instead of baseURL in 2.7.

Version 1.3.1 of ember-cli-htmlbars just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli-htmlbars 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 💪

Your Greenkeeper Bot 🌴

@extend rules are being ignored regardless of rule selected

Version 2.13.2 of ember-cli just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli 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 💪

Your Greenkeeper Bot 🌴

I followed the autoprefixer example in your readme but the CSS does not resolve when serving with ember serve.

ember build compiles the CSS correctly but puts the resulting file in dist/app/styles which I believe should be dist/assets.

Possibly a 2.7 thing? Or just some misconfiguration on my end. If so the examples possibly need updating.

Repo is here:
https://github.com/ashleyconnor/mapledeals_frontend

Version 5.2.0 of ember-cli-babel just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli-babel 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 💪

Your Greenkeeper Bot 🌴

When using resolve (from https://github.com/assetsjs/postcss-assets) the resolved filenames don't get fingerprinted in the final css output.

This probably comes from postcss hooks being run after https://github.com/rickharrison/broccoli-asset-rev 's hooks.

When I use a single plugin, it works fine. But when I use

postcssOptions: {
      compile : {
        plugins: [
          { module: require('autoprefixer') },
          { module: require('postcss-scss') }
        ]
      }
    }

I get this error

The Broccoli Plugin: [PostcssCompiler] failed with:
TypeError: plugin.module is not a function

What am I missing?

Thanks!

Version 7.0.2 of eslint-config-standard just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-standard 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 💪

Your Greenkeeper Bot 🌴

Version 0.4.2 of ember-cli-htmlbars-inline-precompile just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ember-cli-htmlbars-inline-precompile 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 💪

Your Greenkeeper Bot 🌴

I'm trying to use this add-on in a project that's already using ember-cli-sass. I tried every combination of config for both this plugin and outputPaths that I could imagine, but I always get an exception for app/styles/app.css not existing in the tmp build dir. What does exist in there is exactly what I'd expect, i.e. assets/myappname.css.

If you're interested in looking at the exact code and error, you could look at branch in this PR: 67P/hyperchannel#116

Hi folks 👋

I'm working on an addon that needs to process postcss as part of the addon's css. Ideally, I would love for the addons processed css to be a part of vendor.css and for the consuming app to not have to care about it but I would be ok with a system where you need to do something like add @import 'my-cool-plugin.css'; to /app/styles/app.css. (found in the now defunct: https://github.com/adfinis-sygroup/ember-adcssy)

Any advice on how to proceed would be very helpful

Version 3.5.0 of eslint-plugin-promise just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-promise 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 💪

Your Greenkeeper Bot 🌴

When using a pod structure, css files are located in /app/components/*, outside the /app/styles directory, this works when booting ember-cli (ember serve), but doesn’t trigger the PostcssCompiler when changing component stylesheets.

See ember-cli-sass and ember-cli-less for examples of tests.

It seems that out of the box ember-cli-postcss doesn't work together with ember-cli-less

Could it be documented (or fixed) how to setup ember-cli-less -> ember-cli-postcss pipeline?

For comparison, ember-cli-less -> ember-cli-autoprefixer combination works without any special configuration. You just need to install both of them separately.

Having the ability to white/black list vendor dependencies when running the filter method would reduce possible errors and allow for faster processing, as mentioned in #22.

Version 3.0.4 of minimatch just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As minimatch 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 💪

Your Greenkeeper Bot 🌴

Hello, is the plugin function syntax from broccoli-postcss supported here?

I noticed that the versions on github and the versions on npm are not in sync (3.0.5 does not exist on github).