question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[5.0.0] Production Build breaks Styles

See original GitHub issue

Issue type

  • bug report
  • feature request

Issue description

Current behavior: NOTE: I disabled Angular Ivy since ng2-smart-table is NOT compatible with it.

So basically if you have a pretty complex project Ivy is breaking things like i said, i disabled Ivy by turning off aot and buildOptimizer in angular.json. That’s the only way i was able to build my project using 5.0.0.

Since i updated to 5.0.0 when i compile for Production environment styles optimization must be turned off or it can cause some weird glitches.

Maybe something related to RTL or LTR formatting?

Expected behavior: Correct alignment of interface elements.

Steps to reproduce: Add ng-toggle in page and build for Production.

Related code: This is my toggle.

<nb-toggle formControlName="blPreserve">Preserve?</nb-toggle>

Other information:

Screenshot from 2020-03-24 13-33-49 Screenshot from 2020-03-24 13-33-45 Screenshot from 2020-03-24 13-34-44

npm, node, OS, Browser

Node, npm: v12.16.1, 6.13.4
OS: ZorinOS 15.2
Browser: Chrome

Angular, Nebular Angular 9 (Ivy disabled) and Nebular 5.0.0

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:3
  • Comments:5

github_iconTop GitHub Comments

1reaction
macchiecommented, Mar 25, 2020

NOTE4: this is the only solution i found so far…

nb-toggle .toggle.checked .toggle-switcher {
  left: calc(100% - var(--toggle-switcher-size) - var(--toggle-border-width)) !important;
}
0reactions
macchiecommented, Apr 8, 2020

I have the same issue - when running in production the toggle alignment is wrong. I am running the latest Nebular and Angular versions + Ivy enabled.

Same here right now. CSS override was the only solution to me.

Read more comments on GitHub >

github_iconTop Results From Across the Web

node.js - Material-UI Rendering Bugs in production / build
Material-UI have different style result in production mode? 3 · Production environment breaks material-ui styling · 12 · Material UI v5 server ...
Read more >
Xamarin.Forms 5.0.0.1791-pre5 (5.0.0 Pre Release 5 ...
Release notes detailing new features, improvements, and issues fixed in Xamarin.Forms 5.0.0.1791-pre5 (5.0.0 Pre Release 5)
Read more >
Gatsby Changelog | 5.3.0
We are proposing Breaking Changes for the next major version of Gatsby to our GraphQL API. The goal of this change is increasing...
Read more >
Changelog - Sphinx documentation
#9672: The rendering of Python domain declarations is implemented with more docutils nodes to allow better CSS styling. It may break existing styling....
Read more >
sass-loader - webpack - JS.ORG
For production builds it's recommended to extract the CSS from your bundle being able to use parallel loading of CSS/JS resources later on....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found