Skip to content

feat: migrate @atlaskit components to latest compiled-css-in-js major versions #838

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

Merged
merged 2 commits into from
Apr 8, 2025

Conversation

setchy
Copy link
Owner

@setchy setchy commented Apr 8, 2025

closes #467

@github-actions github-actions bot added the dependency Dependency updates label Apr 8, 2025
Copy link

netlify bot commented Apr 8, 2025

Deploy Preview for atlassify canceled.

Name Link
🔨 Latest commit 2011bb7
🔍 Latest deploy log https://app.netlify.com/sites/atlassify/deploys/67f5b03fc02f08000923ada1

Copy link

sonarqubecloud bot commented Apr 8, 2025

@setchy setchy changed the title Feat/compiled migration atlaskit feat: migrate @atlaskit components to latest compiled-css-in-js major versions Apr 8, 2025
@setchy setchy added this to the Release 1.16.0 milestone Apr 8, 2025
@github-actions github-actions bot added the enhancement New feature or enhancement to existing functionality label Apr 8, 2025
@setchy setchy merged commit 3b19d0a into main Apr 8, 2025
20 of 21 checks passed
@setchy setchy deleted the feat/compiled-migration-atlaskit branch April 8, 2025 23:41
use: [
{
// ↓↓ Atlaskit Components with Compiled CSS in JS - must be defined last ↓↓
loader: '@compiled/webpack-loader',

Choose a reason for hiding this comment

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

hey @setchy was this the missing piece?

Copy link
Owner Author

@setchy setchy Apr 9, 2025

Choose a reason for hiding this comment

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

Hey @danieldelcore - not quite. My handful of attempts at migrating had always had this webpack loader defined.

What I did differently this time is i didn't attempt to introduce babel. I mistakenly assumed from the screenshot on https://compiledcssinjs.com/docs/installation#webpack that babel was a requirement. Each time I tried to configure babel in the project, it caused other flow-on impacts. So this time I skipped that and it seems to have worked out ok...

Also, the issue's I were having with my jest unit tests was resolved by adding this to my setup file. without it, jest would fail tests due to not being able to understand the CSS imports

https://github.com/setchy/atlassify/pull/838/files#diff-860bd1f15d1e0bafcfc6f62560524f588e6d6bf56d4ab1b0f6f8146461558730R12-R14

Copy link
Owner Author

@setchy setchy Apr 9, 2025

Choose a reason for hiding this comment

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

I have noticed a few minor visual regression, with modal sizing and with Form field labels.

For now i'm chalking them down to changes in the component library itself and will monitor how they evolve over time

Choose a reason for hiding this comment

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

I think the modal issue is actually a bug, my colleague has a PR up for that right now :) Not sure about form labels, could just be a recent visual change.

Copy link
Owner Author

Choose a reason for hiding this comment

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

I'll share an example of the forms label later today (before and after).

What I noticed is the label is using a normal font-weight instead of being slightly bolded.

Copy link
Owner Author

@setchy setchy Apr 10, 2025

Choose a reason for hiding this comment

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

This is the form field labels which I was referring to.

Before After
2025-03-15T12-01-18 959Z-Atlassify-screenshot 2025-04-10T17-39-54 323Z-Atlassify-screenshot

These used to be a heavier font-weight, similar to the example shown in https://atlassian.design/components/form/examples

Copy link
Owner Author

Choose a reason for hiding this comment

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

I think the modal issue is actually a bug, my colleague has a PR up for that right now :)

Happy to confirm this regression was fixed in @atlaskit/modal-dialog v14.1.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency Dependency updates enhancement New feature or enhancement to existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

migrate build/webpack to use compiled plugins
2 participants