Sam Van Campenhout

I think we also have this problem altough the situation is different. We are switching from ember-cli-sass to ember-cli-postcss. I followed the example in the guides and during builds we...

@jeffjewiss Sorry, it might not have been obvious. We are still using sass. So we are @importing things with Sass. This is our config: ```JavaScript postcssOptions: { compile: { extension:...

@greyhwndz I think you are trying to import sass files without configuring PostCSS to understand that. I think it will work if you configure ember-cli-postcss like [this](https://github.com/jeffjewiss/ember-cli-postcss#switching-from-sass). You won't need...

I think this is a duplicate of this ember issue? https://github.com/emberjs/ember.js/issues/19610 It seems the docs explicitly mention this behavior so it works as intended :smile:.

It seems ember-cli-fastboot v2 isn't compatible with Ember 4+. [This import path](https://github.com/ember-fastboot/ember-cli-fastboot/blob/114a2ad886c9f1cca4427c5dc67435903c1075be/addon/services/fastboot.js#L2) was [deprecated](https://deprecations.emberjs.com/v3.x#toc_old-deprecate-method-paths) and removed in Ember 4 which is the error message you see here. I would try...

@byteg You can just modify the version in you package.json file, but v3 has since been [officially released](https://github.com/ember-fastboot/ember-cli-fastboot/releases/tag/v3.2.0) so you can just update to that version instead. I _think_ that...

It sounds like the same issue as https://github.com/ember-cli/ember-cli/issues/9826 which is caused by the `@babel/parser` v7.17.7 release. Forcing the version to 7.17.3 or lower resolves the issue for now.

This is similar to the issue I created a couple of years ago: https://github.com/miguelcobain/ember-yeti-table/issues/18 But I probably didn't explain it well enough :smile:.

I ran into the `no-unpublished-require` rule as well and the docs explain it pretty good: https://github.com/mysticatea/eslint-plugin-node/blob/master/docs/rules/no-unpublished-require.md#-rule-details In my case it was triggered because `ava` is a devDependency but I didn't...

@NickColley I had the same thoughts and that's indeed a popular request in the eslint-plugin-node repo: https://github.com/mysticatea/eslint-plugin-node/issues/77 Sadly that projects is kind of unmaintained at the moment. I did however...