Update postcss 8.4.35 → 8.4.38 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ postcss (8.4.35 → 8.4.38) · Repo · Changelog

Release Notes

8.4.38

• Fixed endIndex: 0 in errors and warnings (by @romainmenke).

8.4.37

• Fixed original.column are not numbers error in another case.

8.4.36

• Fixed original.column are not numbers error on broken previous source map.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 14 commits:

• Release 8.4.38 version
• Update dependencies
• Merge pull request #1932 from romainmenke/fix-warning-end-index--inventive-numbat-fbada42105
• fix endIndex
• failing test: for endIndex 0 in rangeBy
• Add changelog auto release on Github
• Release 8.4.37 version
• Fix another broken prev source map issue
• Update dependencies
• Release 8.4.36 version
• Use new feature to prevent errors on broken map
• Move to ESLint flat config
• Update CI
• Update dependencies

↗️ source-map-js (indirect, 1.0.2 → 1.2.0) · Repo · Changelog

Release Notes

1.2.0

Allow to pass options to SourceMapGenerator using SourceMapGenerator.fromSourceMap as second argument

var generator = sourceMap.SourceMapGenerator.fromSourceMap(new SourceMapConsumer(), {
  ignoreInvalidMapping: true,
});

• Add generator options to fromSourceMap (#22) @ai

1.1.0

Add ignoreInvalidMapping option to SourceMapGenerator. If enabled, source-map-js will not throw an error on the incorrect previous source map. Instead, it will print warnings and ignore broken mappings.

var generator = new sourceMap.SourceMapGenerator({
  file: "my-generated-javascript-file.js",
  sourceRoot: "http://example.com/app/js/",
  ignoreInvalidMapping: true,
});

• Do not throw an error since broken prev map is popular issue #20 (#20) @ai
• Add ignoreInvalidMapping option (#21) @7rulnik

1.0.3

• Use sourceContents when non-null, even if it's an empty string (#17) @bshepherdson

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 11 commits:

• 1.2.0
• Update changelog
• Fix typo
• Add generator options to fromSourceMap (#22)
• 1.1.0
• Add ignoreInvalidMapping option (#21)
• Do not throw an error since broken prev map is popular issue (#20)
• Update CHANGELOG.md
• 1.0.3
• Update changelog
• Use sourceContents when non-null, even if it's an empty string (#17)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)