Skip to content

test: sourcemaps with an actual plugin #680

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

romainmenke
Copy link

@romainmenke romainmenke commented Jan 29, 2024

This PR contains a:

  • bugfix
  • new feature
  • code refactor
  • test update
  • typo fix
  • metadata update

Motivation / Use-Case

PostCSS has two modes:

  • LazyResult
  • NoWorkResult

NoWorkResult is an optimized path that is taken if no plugins, parsers, ... are provided.
The assumption here is that the user has a bad config and doesn't actually want to use PostCSS.

LazyResult is PostCSS actually doing things.

The sourcemaps generated for both modes are radically different.

This changes adds a noop plugin to trigger the LazyResult mode.

Breaking Changes

N/A

Additional Info

I don't know if this might surface subtle bugs here.
Main purpose is to have better test coverage.

I am trying to pinpoint the cause of this issue : postcss/postcss#1914

Copy link

linux-foundation-easycla bot commented Jan 29, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: romainmenke / name: Romain Menke (4fd2695)

@romainmenke
Copy link
Author

Changed my mind, better not to change these tests unless there is an actual issue.

@romainmenke romainmenke deleted the test-with-plugin--generous-common-frog-40ad9a6e46 branch January 29, 2024 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant