mike-north / ember-materialize-shim Goto Github PK

bower install -V
bower not-cached git://github.com/mike-north/materialize.git#bower-fix
bower resolve git://github.com/mike-north/materialize.git#bower-fix
bower not-cached git://github.com/google/material-design-icons.git#^2.2.1
bower resolve git://github.com/google/material-design-icons.git#^2.2.1
bower cached git://github.com/components/ember.git#2.4.3
bower validate 2.4.3 against git://github.com/components/ember.git#~2.4.1
bower cached git://github.com/ember-cli/ember-cli-test-loader.git#0.2.2
bower validate 0.2.2 against git://github.com/ember-cli/ember-cli-test-loader.git#0.2.2
bower cached git://github.com/ember-cli/ember-cli-shims.git#0.1.0
bower validate 0.1.0 against git://github.com/ember-cli/ember-cli-shims.git#0.1.0
bower cached git://github.com/dockyard/ember-qunit-notifications.git#0.1.0
bower validate 0.1.0 against git://github.com/dockyard/ember-qunit-notifications.git#0.1.0
bower download https://github.com/google/material-design-icons/archive/2.2.3.tar.gz
bower cached git://github.com/components/ember.git#2.4.3
bower validate 2.4.3 against git://github.com/components/ember.git#>=1.4
bower progress material-design-icons#^2.2.1 received 3.8MB of 32.1MB downloaded, 12%
bower progress material-design-icons#^2.2.1 received 4.0MB of 32.1MB downloaded, 13%
bower progress material-design-icons#^2.2.1 received 4.3MB of 32.1MB downloaded, 13%
bower progress material-design-icons#^2.2.1 received 4.6MB of 32.1MB downloaded, 14%
bower progress material-design-icons#^2.2.1 received 4.9MB of 32.1MB downloaded, 15%
bower progress material-design-icons#^2.2.1 received 5.1MB of 32.1MB downloaded, 16%
bower progress material-design-icons#^2.2.1 received 5.4MB of 32.1MB downloaded, 17%
bower progress material-design-icons#^2.2.1 received 5.7MB of 32.1MB downloaded, 18%
bower progress material-design-icons#^2.2.1 received 5.9MB of 32.1MB downloaded, 19%
bower progress material-design-icons#^2.2.1 received 6.2MB of 32.1MB downloaded, 19%
bower progress material-design-icons#^2.2.1 received 6.5MB of 32.1MB downloaded, 20%
bower ENORESTARGET Tag/branch bower-fix does not exist

Additional error details:
Available tags: v0.62, v0.68, v0.69, v0.81, v0.82, v0.9, v0.91, v0.92.0, v0.92.1, v0.93.0, v0.93.1, v0.94.0, v0.94.1, v0.94.2, v0.95.0, v0.95.1, v0.95.2, v0.95.3, v0.96.0, v0.96.1, v0.97.0
Available branches: card-buttons, documentation/old_style, dropdown/rework, dropdown/sibling, gh-pages, master, modal/animation, observer, patch-1, patch-2, revert-1098-patch-1, site-restructure, testem, transitions

Stack trace:
Error: Tag/branch bower-fix does not exist
at createError (/usr/local/lib/node_modules/bower/lib/util/createError.js:4:15)
at /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:15
From previous event:
at GitHubResolver.GitResolver._findResolution (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:158:6)
at GitHubResolver.GitRemoteResolver._findResolution (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitRemoteResolver.js:99:50)
at GitHubResolver.GitResolver._resolve (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:66:17)

Console trace:
Error
at StandardRenderer.error (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:83:37)
at Logger. (/usr/local/lib/node_modules/bower/lib/bin/bower.js:110:26)
at Logger.emit (events.js:107:17)
at Logger.emit (/usr/local/lib/node_modules/bower/lib/node_modules/bower-logger/lib/Logger.js:29:39)
at /usr/local/lib/node_modules/bower/lib/commands/index.js:48:20
at _rejected (/usr/local/lib/node_modules/bower/lib/node_modules/q/q.js:844:24)
at /usr/local/lib/node_modules/bower/lib/node_modules/q/q.js:870:30
at Promise.when (/usr/local/lib/node_modules/bower/lib/node_modules/q/q.js:1122:31)
at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/bower/lib/node_modules/q/q.js:788:41)
at /usr/local/lib/node_modules/bower/lib/node_modules/q/q.js:604:44
System info:
Bower version: 1.7.7
OS: Darwin 15.3.0 x64

We updated materializecss from 0.97.6 to 0.97.7 and ran into following error:

The Broccoli Plugin: [Funnel: Funnel
bower_components/materialize/dist/font/roboto
assets
include:15] failed with:

After that we also updated materialize-shim to 0.2.2, because we found out that the font-dir has changed from materialize/dist/font to materialize/dist/fonts. After the update the error still occurs, because the directory is still wrong in 0.2.2 (index.js).

Should we provide a push-request?

Further we want to know how to properly update ember-cli-materialize, so we dont't have to update the dependencies as well?

As far as I can tell, this "exports" option does not have any effect. (It is not a documented option for app.import in ember-cli v2.18.0 or v2.3.0)
What is it supposed to do?

Hello,

when calling a page for the first time, using Fastboot, I get the error:
Error: Could not find module materialize

The import statement in the component is:

import Materialize from 'materialize';

Any ideas?

thank you so much.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Version 6.3.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.

ember-cli-babel is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hello,

I'm trying to activate my sideNav navigation when page turns to mobile view and I'm unable to use Materialize's Javascript.

I've included this in my ember-cli-build.js, searched around but the last hour of looking around was unfortunately fruitless.

  var app = new EmberApp(defaults, {
    // Add options here
    sassOptions: {
      includePaths: [
        'bower_components/materialize/sass'
      ]
    },
    'materialize-shim': {
      omitJS: true
    }
  });

The CSS works just well, but when I try to call following code from my route/activate() or chrome's console

  $(".button-collapse").sideNav();

I get

  TypeError: $(...).sideNav is not a function

I've tried to include the materialize here and there with the

    import Materialize from 'materialize';

but it always ends up with this error in Chrome's console

    Caught Error: Could not find module `materialize` imported from `konektor/routes/app`

Is there any way to fix this? Am I missing something important? In the readme it says to import the materialize in my-file.js - there is no such file, so I'm not sure what to think of that.

Thank you very much :)

Hi , when i try to install ember-materialize-shim, i am getting this below error.

Command failed: npm install --save-dev --loglevel error ember-cli-sass@~5.4.0 ember-material-design-icons-shim@~0.1.9
npm WARN deprecated [email protected]: ..psst! While Bower is maintained, we recommend Yarn and Webpack for new front-end projects!
Yarn's advantage is security and reliability, and Webpack's is support for both CommonJS and AMD projects. Currently there's n
o migration path, but please help to create it: bower/bower#2467
npm ERR! path E:\node\q-manager\node_modules.node-sass.DELETE\vendor\win32-x64-48\binding.node
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall unlink
npm ERR! Error: EPERM: operation not permitted, unlink 'E:\node\q-manager\node_modules.node-sass.DELETE\vendor\win32-x64-48\bi
nding.node'
npm ERR! at Error (native)
npm ERR! { Error: EPERM: operation not permitted, unlink 'E:\node\q-manager\node_modules.node-sass.DELETE\vendor\win32-x64-48
\binding.node'
npm ERR! at Error (native)
npm ERR! cause:
npm ERR! { Error: EPERM: operation not permitted, unlink 'E:\node\q-manager\node_modules.node-sass.DELETE\vendor\win32-x64-
48\binding.node'
npm ERR! at Error (native)
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path: 'E:\node\q-manager\node_modules\.node-sass.DELETE\vendor\win32-x64-48\binding.node' },
npm ERR! stack: 'Error: EPERM: operation not permitted, unlink 'E:\node\q-manager\node_modules\.node-sass.DELETE\vendor
\win32-x64-48\binding.node'\n at Error (native)',
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path: 'E:\node\q-manager\node_modules\.node-sass.DELETE\vendor\win32-x64-48\binding.node',
npm ERR! parent: 'q-manager' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Samuel\AppData\Roaming\npm-cache_logs\2017-08-19T03_55_46_537Z-debug.log

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): sass
• chore(deps): stable ember infrastructure (minor) (ember-cli, ember-cli-htmlbars, ember-source, eslint-plugin-ember, eslint-plugin-node)
• chore(deps): ember-try
• chore(deps): husky
• fix(deps): stable ember infrastructure (major) (ember-cli-babel, ember-resolver, eslint-plugin-ember)
• chore: lockfile maintenance
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• fix(deps): broccoli-funnel
• fix(deps): broccoli-merge-trees

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): semantic-release [security]
• chore(deps): commitlint monorepo (patch) (@commitlint/cli, @commitlint/config-conventional, @commitlint/travis-cli)
• chore(deps): ember-cli-fastboot
• chore(deps): ember-try
• chore(deps): husky
• chore(deps): commitlint monorepo (major) (@commitlint/cli, @commitlint/config-conventional, @commitlint/travis-cli)
• chore(deps): ember-source-channel-url
• fix(deps): ember-cli-sass
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Running ember test on my local gives this error:

Cannot find module 'os-locale/' from '/Users/dustin/Archive/ember-materialize-shim/node_modules/yargs/'
Error: Cannot find module 'os-locale/' from '/Users/dustin/Archive/ember-materialize-shim/node_modules/yargs/'
    at Function.module.exports [as sync] (/Users/dustin/Archive/ember-materialize-shim/node_modules/resolve/lib/sync.js:33:11)
    at resolvePkg (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/resolve-pkg.js:20:18)
    at pkg (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/pkg.js:17:20)
    at again (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:18:22)
    at /Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:27:7
    at Array.forEach (native)
    at again (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:26:55)
    at /Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:27:7
    at Array.forEach (native)
    at again (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:26:55)
    at /Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:27:7
    at Array.forEach (native)
    at again (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:26:55)
    at /Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:27:7
    at Array.forEach (native)
    at again (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:26:55)
    at /Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:27:7
    at Array.forEach (native)
    at again (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:26:55)
    at depsFor (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/deps-for.js:29:4)
    at statPathsFor (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/lib/stat-paths-for.js:14:15)
    at hashForDep (/Users/dustin/Archive/ember-materialize-shim/node_modules/hash-for-dep/index.js:15:21)

I poked around yargs a bit and haven't found anything obvious. Will continue to investigate.

I have tried this 6 ways to Sunday, and can't get this shim to work with Fastboot.

Details:

ember-cli: 2.14.1
node: 7.10.0
os: linux x64

package.json:

"devDependencies": {
    "broccoli-asset-rev": "^2.4.5",
    "ember-ajax": "^3.0.0",
    "ember-cli": "~2.14.1",
    "ember-cli-app-version": "^3.0.0",
    "ember-cli-babel": "^6.3.0",
    "ember-cli-dependency-checker": "^1.3.0",
    "ember-cli-eslint": "^3.0.0",
    "ember-cli-fastboot": "^1.0.2",
    "ember-cli-htmlbars": "^2.0.1",
    "ember-cli-htmlbars-inline-precompile": "^0.4.3",
    "ember-cli-inject-live-reload": "^1.4.1",
    "ember-cli-qunit": "^4.0.0",
    "ember-cli-sass": "^5.4.0",
    "ember-cli-shims": "^1.1.0",
    "ember-cli-sri": "^2.1.0",
    "ember-cli-uglify": "^1.2.0",
    "ember-data": "~2.14.3",
    "ember-export-application-global": "^2.0.0",
    "ember-load-initializers": "^1.0.0",
    "ember-material-design-icons-shim": "^0.1.11",
    "ember-materialize-shim": "^0.4.2",
    "ember-resolver": "^4.0.0",
    "ember-source": "~2.14.1",
    "ember-welcome-page": "^3.0.0",
    "loader.js": "^4.2.3"

bower.json:

 "dependencies": {
    "materialize": "0.97.7"
}

If I install nothing but the shim, I can start a new project and it runs fine (despite not finding the sass files, but that seems like an easy fix)

As soon as I install Fastboot, though, I get the following error:

TypeError: Cannot read property 'swing' of undefined
    at projects/ember-test/ui/tmp/broccoli_merge_trees-output_path-qEM9Moxv.tmp/assets/bower_components/materialize/dist/js/materialize.js:55:1
    at ContextifyScript.Script.runInContext (vm.js:32:29)
    at VMSandbox.eval (projects/ember-test/ui/node_modules/fastboot/src/vm-sandbox.js:14:16)
    atprojects/ember-test/ui/node_modules/fastboot/src/ember-app.js:136:15
    at Array.forEach (native)
    at EmberApp.loadAppFiles (projects/ember-test/ui/node_modules/fastboot/src/ember-app.js:133:21)
    at EmberApp.retrieveSandboxedApp (projects/ember-test/ui/node_modules/fastboot/src/ember-app.js:181:10)
    at new EmberApp (projects/ember-test/ui/node_modules/fastboot/src/ember-app.js:49:21)
    at FastBoot._buildEmberApp (projects/ember-test/ui/node_modules/fastboot/src/index.js:114:17)
    at new FastBoot (projects/ember-test/ui/node_modules/fastboot/src/index.js:52:10)
    at app.use (projects/ember-test/ui/node_modules/ember-cli-fastboot/index.js:247:29)
    at Layer.handle [as handle_request] (projects/ember-test/ui/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (projects/ember-test/ui/node_modules/express/lib/router/index.js:317:13)
    atprojects/ember-test/ui/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (projects/ember-test/ui/node_modules/express/lib/router/index.js:335:12)
    at next (projects/ember-test/ui/node_modules/express/lib/router/index.js:275:10)
    at err (projects/ember-test/ui/node_modules/ember-cli/lib/tasks/server/middleware/broccoli-watcher/index.js:54:11)
    at watcher.then (projects/ember-test/ui/node_modules/broccoli-middleware/lib/watcher-middleware.js:35:7)
    at tryCatch (projects/ember-test/ui/node_modules/rsvp/dist/lib/rsvp/-internal.js:198:12)
    at invokeCallback (projects/ember-test/ui/node_modules/rsvp/dist/lib/rsvp/-internal.js:211:13)
    at projects/ember-test/ui/node_modules/rsvp/dist/lib/rsvp/then.js:26:14
    at flush (projects/ember-test/ui/node_modules/rsvp/dist/lib/rsvp/asap.js:80:5)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)

Am I doing something wrong?

Now that ember-auto-import is available, it seems that a lot of these "shim" addons can be deprecated. Are there still good reasons to keep using this one?

On registry https://registry.npmjs.org/, the "latest" version (v1.8.4) of dependency bower has the following deprecation notice:

We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about bower's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

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.

ember-cli-htmlbars is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

On registry https://registry.npmjs.org/, the "latest" version (v0.1.0) of dependency exists-sync has the following deprecation notice:

Please replace with usage of fs.existsSync

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about exists-sync's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

In #25 there was an issue running tests. Turns out npm is not installing two dependencies required by yargs: os-locale and y18n.

As a workaround, we are pegging manually in our own package.json, but this should be resolved in a more elegant way.

When running ember test on a fresh project using [email protected], I get the below. I tried importing materialize.js myself in ember-cli-build.js and got the same, so this isn't an issue with the shim per se...

not ok 1 PhantomJS 1.9 - Global error: TypeError: 'undefined' is not a function
(evaluating 'document.querySelectorAll.bind(document)') at http://localhost:7357
/assets/vendor.js, line 66517
    ---
        Log: |
            { type: 'error',
              text: 'TypeError: \'undefined\' is not a function (evaluating \'do
cument.querySelectorAll.bind(document)\') at http://localhost:7357/assets/vendor
.js, line 66517\n' }

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Hi,
I get the following error while compiling..

File: /Users/myuser/Desktop/myapp/ui/tmp/sass_compiler-input_base_path-Ktf1Enx4.tmp/0/app/styles/app.scss (5)
The Broccoli Plugin: [SassCompiler] failed with:
Error: File to import not found or unreadable: materialize
Parent style sheet: /Users/myuser/Desktop/myapp/ui/tmp/sass_compiler-input_base_path-Ktf1Enx4.tmp/0/app/styles/app.scss
    at options.error (/Users/myuser/Desktop/myapp/ui/node_modules/ember-cli-sass/node_modules/broccoli-sass-source-maps/node_modules/node-sass/lib/index.js:277:32)

The broccoli plugin was instantiated at:
    at SassCompiler.Plugin (/Users/myuser/Desktop/myapp/ui/node_modules/broccoli-caching-writer/node_modules/broccoli-plugin/index.js:10:31)
    at SassCompiler.CachingWriter [as constructor] (/Users/myuser/Desktop/myapp/ui/node_modules/broccoli-caching-writer/index.js:21:10)
    at new SassCompiler (/Users/myuser/Desktop/myapp/ui/node_modules/ember-cli-sass/node_modules/broccoli-sass-source-maps/index.js:20:17)
    at /Users/myuser/Desktop/myapp/ui/node_modules/ember-cli-sass/index.js:27:12
    at Array.map (native)
    at SASSPlugin.toTree (/Users/myuser/Desktop/myapp/ui/node_modules/ember-cli-sass/index.js:24:34)
    at /Users/myuser/Desktop/myapp/ui/node_modules/ember-cli-preprocess-registry/preprocessors.js:184:26
    at Array.forEach (native)
    at processPlugins (/Users/myuser/Desktop/myapp/ui/node_modules/ember-cli-preprocess-registry/preprocessors.js:182:11)
    at module.exports.preprocessCss (/Users/myuser/Desktop/myapp/ui/node_modules/ember-cli-preprocess-registry/preprocessors.js:152:10)