Skip to content
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

fix: tailwind css sourcemap warning #7480

Merged
merged 1 commit into from Mar 29, 2022

Conversation

sapphi-red
Copy link
Member

Description

#7432

fixes Sourcemap for "/path/to/tailwind.css" points to missing source files. with postcss virtual files.

Additional context

It seems tailwind returns <input css foobar> as a path in sourcemap.sources.
Since postcss uses <no source>, I thought postcss uses <something> to indicate a virtual file.
Though I did not find any documents about it.


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Before submitting the PR, please make sure you do the following

  • Read the Contributing Guidelines.
  • Read the Pull Request Guidelines and follow the Commit Convention.
  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
  • Ideally, include relevant tests that fail without this PR but pass with it.

@sapphi-red sapphi-red force-pushed the fix/tailwind-sourcemap-warning branch 4 times, most recently from 1b823a5 to 4e12359 Compare March 29, 2022 07:11
@sapphi-red sapphi-red force-pushed the fix/tailwind-sourcemap-warning branch from 4e12359 to 827bb14 Compare March 29, 2022 07:16
@patak-dev patak-dev merged commit 90df0bb into vitejs:main Mar 29, 2022
@sapphi-red sapphi-red deleted the fix/tailwind-sourcemap-warning branch March 30, 2022 07:20
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.

None yet

2 participants