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

Warning about conflicts with css order of importing #475

Merged
merged 9 commits into from
Sep 3, 2024

Conversation

Brenosalv
Copy link
Collaborator

Changes

  • Ignore the warning since CSS Modules are scoped to a component and the order of importing does not matter.

Tests / Screenshots

  • Tested locally and the warnings are not displayed.

@Brenosalv Brenosalv added the tech debt This is a task that really only the engineers notice label Sep 2, 2024
@Brenosalv Brenosalv self-assigned this Sep 2, 2024
@Brenosalv Brenosalv linked an issue Sep 2, 2024 that may be closed by this pull request
Copy link

github-actions bot commented Sep 2, 2024

Visit the preview URL for this PR (updated for commit d7ce5d2):

https://estuary-marketing--pr475-brenosalv-tech-debt-2v6gxzmf.web.app

(expires Thu, 03 Oct 2024 18:14:11 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 76f6b095a0752e5d9c6c890267f9fdc3e392161e

gatsby-node.ts Outdated Show resolved Hide resolved
@Brenosalv
Copy link
Collaborator Author

Fixing another warning:
image

It seems like this happens when we set align-items: start or end instead of align-items: flex-start or flex-end. I added flex and the warning disappeared.

gatsby-node.ts Outdated
@@ -445,3 +445,16 @@ export const createResolvers: GatsbyNode['createResolvers'] = async ({
},
});
};

export const onCreateWebpackConfig = ({ stage, actions, getConfig }) => {
if (stage === 'develop') {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should probably keep this on for build-javascript as well.

I know the warning does not show up in prod but probably good to keep these configs in sync.

Copy link
Member

@travjenkins travjenkins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm - pulled locally and ran a build and worked fine

@travjenkins travjenkins merged commit 9718758 into master Sep 3, 2024
1 check passed
@travjenkins travjenkins deleted the Brenosalv/tech-debt/css-order-conflicts-warning branch September 3, 2024 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech debt This is a task that really only the engineers notice
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CSS order conflicts warning
2 participants