Refactor webpack rule test to support 'postcss' as a lang/file-extension #40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Laravel Mix and VSCode's Vetur plugin are quite at odds with how to specify that you wish to use PostCSS in your VueJS single-file component. I have used some custom configuration in my project to support
<style lang="postcss">for my NPM builds, but Storybook (in particular, this postcss addon) does not yet recognise this customisation.I have updated the css rule test to allow a developer to specify
<style lang="postcss">in their single-file components to ensure Vetur and linting tools correctly recognise the code, while still supporting the same compilation when using the default<style>element.