For some reason (still trying to figure out why) livereload stopped working for me on localhost and it stoped while I wasnt working on a theme but 'bundle exec. Isn't the encapsulation controlled by the imports. Currently if you have enabled livereload in a Omega theme and livereload is not present or not working, you get a '(failed) net::ERRCONNECTIONTIMEDOUT' but also it hungs up a page loading and it tries to load it for 30 seconds or so. Now the only thing "disturbing" here is the css encapsulation i guess. This way i end up having all classes/variables everywhere available and i import boostrap only once and don't have to de-dup in the end. So i got another approach - i'm importing my scss only at one single point in the whole app - in my bootstrapping "" -> and my basic scss is importing bootstrap, and all subsequent scss files of all components. But this results in having bootstrap included several times in the final package - and then i have to de-dup everything? This feels totally wrong to me. But then i don't know all the variables/classes inside my component script - then i have to import everything needed over and over again in every component (which is not wrong as i read about ES6 modules). I know it would be perfect in ES6 modules to import the css for every component directly in the components code. My problem is, i try to use Sass together with Bootstrap. but, how would i turn off css encapsulation for a component? Thanks for your replies! Everything clear so far. Page should not reload at least with css - what the state is with HMR i don't really know. watch webpack rebuilding the package and as soon as he is ready -> the page reloads.open up home.css for example and add some css like body.checkout the repo as a new project and npm i, npm start.it wasn't made with this new angular2-hmr package). ![]() Now i've upgraded my project with all the new changes and the livereload is broken now, he always reloads the page - on css changes and in typescript (in typescript it was kind of working with the HMR back those days. By livereload i mean, he can inject the new css directly into the browser without reloading the page. Three weeks ago i've initialized a new project with this skeleton project - and the css livereload was working fine. ![]() ![]() It feels like a bug to me but i don't want to stress anybody - the HMR thing is still in developement i guess and maybe it is just work-in-progress.? Scroll not working using angularJS ng-repeat I have live streaming using socket.io, i have set max-height for window to implement scroll bar, but i noticed after reaching to certain point scroll bar does not work and does not display messages, I can see messages are being logged into event but vertical scroll bar is not extending anymore. Do you want to request a feature or report a bug?.Question about the decisions made in the repository
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |