Patrick Berkeley
Patrick Berkeley
FWIW this is the same issue as https://github.com/poteto/ember-changeset/issues/485
This is a big trap. Any app that consumes an addon that exports a file that matches the name of a file in the app will sporadically get a bad...
@lolmaus we have hacked around this by creating a `-private` directory for our TS files, then re-exporting from the a JS file at the normal position in the tree. Example...
@TheLooseCannon this is our current approach: https://github.com/typed-ember/ember-cli-typescript/issues/780#issuecomment-576318921
FWIW here is how to install node-sass: `npm install --save-dev node-sass`, then in ember-cli-build.js file: ```js const nodeSass = require('node-sass'); const app = new EmberApp({ sassOptions: { implementation: nodeSass }...
@samselikoff can we keep this open until ember-cli-mirage updates to a version of miragejs that includes miragejs/miragejs#262?
Thanks for reopening and the info @samselikoff !
FWIW https://github.com/Addepar/ember-classy-page-object allows this.
I'm running into needing this. We use ember-cli-page-object in a number of apps and addons. Now we would like to reuse those page objects outside of ember for end-to-end testing...
webpack is [required for `ember-auto-import` v2](https://github.com/ef4/ember-auto-import/blob/master/docs/upgrade-guide-2.0.md) so I'm assuming somehow auto import was upgraded. I don't see ember-auto-import v2 as a requirement for ember 3.27, so is there a chance...