after upgrading Angular from version 8 to 11, fonts are looking different, they are blurred. Any ideas what can I do/check to make them look the same as they were before? Any help would be appreciated. When I run app locally, it looks better than on deployment environment.
You might be hit by something similar to this issue.
There is a new optimization for fonts - external font definitions are inlined as part of the production build. According to the bug above, it might not work in some cases.
Try disabling the fonts inlining optimization in angular.json - https://angular.io/guide/workspace-config#fonts-optimization-options
Related
While using Next.js + Tailwind + DaisyUI in development on Mac everything works as expected and all styles look normal, however when developing on WSL I noticed that my styles look very different and are pretty much broken from what I would expect. I'm encountering this same issue when deploying my site to Vercel. Does anyone know how I can resolve this?
Development (Mac)
Deployment (Vercel)
tailwind.config.js
I attempted to recreate the issue on my mac with no luck, however it seems this issue is showing up on Linux and Vercel deployment.
Update:
Turns out the issue stemmed from the fact that I had a css file in my styles folder and when I imported it into my homepage, it messed up the styling for everything else.
Not sure if this is supposed to be the expected behavior, but it did solve the issue
I'm looking to install Webpack4 for a project.
Part of what I want it to do is lint css.
Just about every resource I find points to "stylelint-webpack-plugin" (https://github.com/JaKXz/stylelint-webpack-plugin).
That project's not been getting updated for a long time.
From what I can tell the webpack team bullied the dev responsibile for lots of the work on stylelint-webpack-plugin right out of the community.
So now the project's got nobody doing the work and it's "looking for a maintainer". After that whole mess, doesn't look like anyone's signing up.
From my perspective -- Oh Well! Next !?
Is there a different alternative to stylelint-webpack-plugin for lint-ing styles in a webpack setup?
The stylelint-webpack-plugin now belongs to the official webpack-contrib GitHub organisation. The plugin's dependencies are up-to-date and it supports the latest version of stylelint (version 9).
I believe it is the still the most appropriate plugin for using stylelint within Webpack.
Purchased a theme for my new app, which is entirely based on LESS. However, Meteor is not recognizing the #varable variables in the LESS files. I have over 100+ such files and these error lines span for that long as well.
Is there anything that I'm doing wrong here by assuming Meteor will compile all the files because the layout isn't working correctly and these LESS file problems are the reason. Anything I can do to fix this problem?
Please check if the version of less used in your purchased theme is compatible with the version of Meteor that your app is using. I had a similar issue recently where my purchased theme used an older version of less which was not compatible with Meteor 1.2. So, when I updated my app to the latest version of Meteor, my app layout was messed up as the less files were not properly interpreted. Please see Breaking changes in Meteor 1.2 - point 3 under Build tool and package improvements
Just my $0.02
I'm a starter in writing app code in Visual Studio 2013 Community Apache Cordova and have managed to connect VS2013 with my Mac. Once I have gone through the process of building the app in VS and on my Mac and installing in on my iPhone, I open it up and it won't rotate. It doesn't rotate for a number of basic apps that I've written nor does it rotate if I build the default new project "Hello, your application is ready!" app.
I have done some research and tried changing the config.xml "Orientation" preference to "both", through the code window and also in the designer window but that doesn't change anything. I've also noticed that adding in a "BackgroundColor" preference doesn't work either.
Does anyone know if I may have configured something incorrectly or perhaps need to add something to my code?
All the HTML, JS and CSS that I've written seems to work okay (with the exception of trying to link URLs to the Safari Browser but that's another issue).
I have noticed the same issues. I tried finding some settings to fix that in the config.xml, but was not successful. I have resolved myself to just opening the iOS project in XCode and changing a few things:
Device Orientation: no matter the config.xml setting, its always only Portrait. I click-check the other 3 orientations.
Team: I have multiple developer profiles, and I need to choose correct one here.
Bundle Identifier. I screwed up one project, and have different case for iOS and Android. I leave the VS one as the Android one, so I can build completely correct for Android. Since I know I have to go to XCode for iOS anyway, I change the bundle identifier here.
You can find the project using Finder at ~/remote-builds/builds/9999/cordovaApp/platforms/ios/*.xcodeproj, where 9999 is the build number, though not necessarily the latest, largest number, but the latest datetime of the folder.
You can also refer to Greg's answer in this related post as an alternative solution.
I have a Ransack search and Foundation in my Rails app and locally css renders ok while the same app in production has a quirk:
other things in the app are exactly the same.
I tested in Chrome and Safari - locally ok, production not ok.
Where can I start troubleshooting this?
UPDATE: I tried to run in production locally (assets:precompile) and it's the same as on the server... so how come asset compilation can change something?
One of the sites probably has a global css selector that set the margin or padding (can't really tell from your example).
Go to the production site and inspect one of the elements. You should see a difference in its computed style.