Bump postcss and ember-css-modules

[dependabot]

Bumps postcss to 8.4.14 and updates ancestor dependency ember-css-modules. These dependencies need to be updated together.

Updates postcss from 7.0.35 to 8.4.14

Release notes

Sourced from postcss's releases.

8.4.14

• Print “old plugin API” warning only if plugin was used (by @​zardoy).

8.4.13

• Fixed append() error after using .parent (by @​thecrypticace).

8.4.12

• Fixed package.funding to have same value between all PostCSS packages.

8.4.11

• Fixed Declaration#raws.value type.

8.4.10

• Fixed package.funding URL format.

8.4.9

• Fixed package.funding (by @​mondeja).

8.4.8

• Fixed end position in empty Custom Properties.

8.4.7

• Fixed Node#warn() type (by @​ybiquitous).
• Fixed comment removal in values after ,.

8.4.6

• Prevented comment removing when it change meaning of CSS.
• Fixed parsing space in last semicolon-less CSS Custom Properties.
• Fixed comment cleaning in CSS Custom Properties with space.
• Fixed throwing an error on .root access for plugin-less case.

8.4.5

• Fixed raws types to make object extendable (by @​43081j).
• Moved from Yarn 1 to pnpm.

8.4.4

• Fixed absolute path in source map on zero plugins mode.

8.4.3

• Fixed this.css.replace is not a function error.

8.4.2

• Fixed previous source map support in zero plugins mode.

8.4.1

• Fixed Stringifier types (by @​43081j).

8.4 “President Camio”

... (truncated)

Changelog

Sourced from postcss's changelog.

8.4.14

• Print “old plugin API” warning only if plugin was used (by @​zardoy).

8.4.13

• Fixed append() error after using .parent (by Jordan Pittman).

8.4.12

• Fixed package.funding to have same value between all PostCSS packages.

8.4.11

• Fixed Declaration#raws.value type.

8.4.10

• Fixed package.funding URL format.

8.4.9

• Fixed package.funding (by Álvaro Mondéjar).

8.4.8

• Fixed end position in empty Custom Properties.

8.4.7

• Fixed Node#warn() type (by Masafumi Koba).
• Fixed comment removal in values after ,.

8.4.6

• Prevented comment removing when it change meaning of CSS.
• Fixed parsing space in last semicolon-less CSS Custom Properties.
• Fixed comment cleaning in CSS Custom Properties with space.
• Fixed throwing an error on .root access for plugin-less case.

8.4.5

• Fixed raws types to make object extendable (by James Garbutt).
• Moved from Yarn 1 to pnpm.

8.4.4

• Fixed absolute path in source map on zero plugins mode.

8.4.3

• Fixed this.css.replace is not a function error.

8.4.2

• Fixed previous source map support in zero plugins mode.

8.4.1

• Fixed Stringifier types (by James Garbutt).

8.4 “President Camio”

• Added ranges for errors and warnings (by Adaline Valentina Simonian).
• Added Stringifier types (by James Garbutt).

... (truncated)

Commits

• b7d1836 Release 8.4.14 version
• 57006b4 Update dependencies
• 2a97ab8 Merge pull request #1744 from zardoy/patch-1
• 6447b55 Merge pull request #1747 from ben-lau/main
• e36ed17 Update plugins.md
• 24f2efc Update depedencies
• 9bda624 Try to fix CI
• 7cd8e27 improve warnings count testing
• 2295e28 fix tests
• fc19f1b fix: print deprecation warning only when plugin is used
• Additional commits viewable in compare view

Updates ember-css-modules from 1.3.4 to 1.6.2

Release notes

Sourced from ember-css-modules's releases.

v1.6.2

No changes noted.

v1.6.0

Added

• You can now pass patchClassicComponent: false in your ECM config to opt out of the deprecated monkeypatching of Ember.Component that will be removed entirely in 2.0 (thanks @​SergeAstapov!)

Fixed

• Modules whose path includes the name of the package they're in no longer cause issues when resolving @value and composes: directives (thanks @​eric162 and @​maxfierke!)

v1.5.0

Deprecated

• ECM's support for binding local class names on the root element of a classic Ember.Compnent (the localClassNames and localClassNameBindings properties and the @localClassName and @localClassNames decorators) has been deprecated and will be removed in the next major release. These APIs rely on reopening Ember.Component (which is itself now deprecated) and can be replaced by several alternative patterns. See the Upgrade Notes section below for migration suggestions.

Upgrade Notes

For classic @ember/component subclasses, ember-css-modules has had support for binding static and dynamic local class names to the component's root element using either .extend() or decorator syntax:

export default Component.extend({
  localClassNames: ['always-present'],
  localClassNameBindings: ['flipACoin'],
flipACoin: computed(function() {
return Math.random() > 0.5 ? 'yes-class' : 'no-class';
}),
});

@localClassNames('always-present')
export default class MyComponent extends Component {
  @localClassName flipACoin = Math.random() > 0.5 ? 'yes-class' : 'no-class';
}

Both versions of these APIs are now deprecated, as:

1. they rely on monkey-patching Ember.Component, which is itself now deprecated
2. they're parallels of the classNames and classNameBindings APIs that are no longer relevant in modern Ember applications

Depending on your appetite for refactoring and modernizing, you might take one of three approaches to migrating off of these APIs:

1. Convert your components to use the modern @glimmer/component base class instead of @ember/component. Since Glimmer component templates have "outer HTML" semantics, there's no implicit root element for these APIs to apply to. See the Octane vs Classic cheat sheet for further details on the differences between classic and Glimmer components.
2. Use tagName: '' to remove the implicit root element from your classic component, then add a corresponding explicit root element to your template, where you can use local-class as you would for any other element.
3. Import the class name mapping from your styles module and use that with the classic classNames and classNameBindings APIs:

   import styles from './styles';
   export default Component.extend({
   classNames: [styles['always-present']],
   classNameBindings: ['flipACoin'],

... (truncated)

Changelog

Sourced from ember-css-modules's changelog.

1.6.2 (March 23, 2021)

Fixed

• Avoid triggering (ember.js#19392)[https://github-redirect.dependabot.com/[Bug] Ember's template compiler on 3.25 complains about ~ in a comment emberjs/ember.js#19392] when we produce synthetic class AttrNodes.

1.6.0 (November 19, 2021)

Added

• You can now pass patchClassicComponent: false in your ECM config to opt out of the deprecated monkeypatching of Ember.Component that will be removed entirely in 2.0 (thanks @​SergeAstapov!)

Fixed

• Modules whose path includes the name of the package they're in no longer cause issues when resolving @value and composes: directives (thanks @​eshirley and @​maxfierke!)

1.5.0 (July 6, 2021)

Deprecated

• ECM's support for binding local class names on the root element of a classic Ember.Compnent (the localClassNames and localClassNameBindings properties and the @localClassName and @localClassNames decorators) has been deprecated and will be removed in the next major release. These APIs rely on reopening Ember.Component (which is itself now deprecated) and can be replaced by several alternative patterns. See the Upgrade Notes section below for migration suggestions.

Upgrade Notes

For classic @ember/component subclasses, ember-css-modules has had support for binding static and dynamic local class names to the component's root element using either .extend() or decorator syntax:

export default Component.extend({
  localClassNames: ['always-present'],
  localClassNameBindings: ['flipACoin'],
flipACoin: computed(function() {
return Math.random() > 0.5 ? 'yes-class' : 'no-class';
}),
});

@localClassNames('always-present')
export default class MyComponent extends Component {
  @localClassName flipACoin = Math.random() > 0.5 ? 'yes-class' : 'no-class';
}

Both versions of these APIs are now deprecated, as:

1. they rely on monkey-patching Ember.Component, which is itself now deprecated
2. they're parallels of the classNames and classNameBindings APIs that are no longer relevant in modern Ember applications

Depending on your appetite for refactoring and modernizing, you might take one of three approaches to migrating off of these APIs:

1. Convert your components to use the modern @glimmer/component base class instead of @ember/component. Since Glimmer component templates have "outer HTML" semantics, there's no implicit root element for these APIs to apply to. See the Octane vs Classic cheat sheet for further details on the differences between classic and Glimmer components.
2. Use tagName: '' to remove the implicit root element from your classic component, then add a corresponding explicit root element to your template, where you can use local-class as you would for any other element.
3. Import the class name mapping from your styles module and use that with the classic classNames and classNameBindings APIs:

   import styles from './styles';
   export default Component.extend({
   classNames: [styles['always-present']],
   classNameBindings: ['flipACoin'],

... (truncated)

Commits

• b85fad1 Avoid triggering ember.js#19392 with synthetic attr nodes (#271)
• 91a3ff3 Disable ember-try for 1.x CI
• 1929b4f Add ember-auto-import to devDeps for ember-try scenarios
• df5892a Swap 1.x backport branch name for automation compatibility
• f5671c1 v1.6.1
• a46b6c8 Allow ember-cli-htmlbars@6
• 794ffbe v1.6.0
• 7733f23 Incorporate @​maxfierke's tests from #226
• e5cea56 Merge pull request #251 from SergeAstapov/fn/opt-out-ember-global
• dbd3154 Merge pull request #250 from Eric162/fix-resolve-path
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by salsify-jenkins-ci, a new releaser for ember-css-modules since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.