What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi all, I posted this issue a while ago, but here we go again (sorry, don't want to annoy you all, j
Hi all,
I posted this issue a while ago, but here we go again (sorry, don't want to annoy you all, just trying to figure out, where it could come from - today I got to this topic again and found out): All of my own css-classes and id's are loaded 66 times (didn't find anything which could explain this specific number)
My project/public/Yves/assets/css/yves_default.app.css
is about 6MB big at 50.000 lines. I guess it is likely that it actually should be less than 1000 Lines.
How many lines does your file have? Are some elements there mutiple times? π€
Comments
-
Found this thread, too: https://sprykercommunity.slack.com/archives/CKJRJM5FG/p1568383690070300
Just wanted to know, if someone else had this before, too. Would it be helpful to just move the shared.scss?
0 -
apparently one of our projects has 22.5k lines in that file. Another has "just" 7k
0 -
With nearly same amount of css?
0 -
one project has 22.5k another project 7k (the other project is older)
0 -
don't know anymore though, just looking π
0 -
Does this appear to be correct to you? Don't know if you did a ton of css π
You could easily check this by scrolling through developer tools of your browser. body tag is already loaded that often in my case0 -
-
body {
is only defined once in theyves_default.app.css
file0 -
It looks like something is wrong with
shared.scss
. Everything is in this file is used by webpack sass-resources-loader and will be added to every endpoint. So by design only variables/functions/mixins definitions should be included intoshared.scss
.0 -
Good hint @UN6T8SEM7 - There was a
@import '~ShopUi/styles/shared';
hiding in the shared.scss.That's probably importing the shared.scss over and over again.. And this would even match at
frontend:yves:build
:Scanning for component styles... 64 found
0 -
I actually thought that the shared.scss is the place to go whenever you want to do any css changes.
0 -
You can take a look into the frontend documentation to understand better where to put your code https://documentation.spryker.com/front-end_developer_guide/yves/atomic-frontend.htm#sass-layer
0 -
Thank you @UN6T8SEM7 π
0 -
The linked issue in your 2nd comment in the thread is still outstanding I believe, and is something in vendor π
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 929 Developer Corner
- 787 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random