![]() ![]() HINT: here you would place all of your js related tasks, e.g. pipe( sourcemaps.write( )) // Reloads style.css if that is enqueued. Use a specific port (instead of the one auto-detected by Browsersync).ĭebounceDelay: 1000 // This introduces a small delay when watching for file change events to avoid triggering too many reloads ![]() Var livereload = require('gulp-livereload') I also installed the browser extension and enabled access to page URLS. var cssnano = require('gulp-cssnano') Issue compiling SASS and SCSS with LiveReload I just installed LiveReload on my Macbook running Catalina 10.15.6 (19G73). var runSequence = require('run-sequence') var imagemin = require('gulp-imagemin') Var browserSync = require('browser-sync').create() Var sourcemaps = require('gulp-sourcemaps') Var autoprefixer = require('gulp-autoprefixer') Var projectPHPWatchFiles = '*.php' // Path to all PHP files. Var customJSWatchFiles = 'js/*.js' // Path to all custom JS files. Var vendorJSWatchFiles = 'js/vendor/*.js' // Path to all vendor JS files. Var styleWatchFiles = 'scss/**/*.scss' // Path to all *.scss files inside css folder and inside them. You can configure Grunt to watch the compiled css file in your dist directory, which would be updated every time the Sass is recompiled. Var styleDestination = '' // Path to place the compiled CSS file. Var styleSRC = 'scss/style.scss' // Path to main. Could be something like v or localhost:8888. If you do, to test something out or what have you, run rails assets:clobber when you are done, to restore your assets to working in development mode.Here’s my gulp file: var projectURL = '' // Local project URL of your already running WordPress site. You generally should not run rails assets:precompile in development. you may or may not still be having problems with actual live-reload, but they'll be different problems - right now, you are having a different problem before you even get to live-reload. Now, try again all of the things you tried before - without the production-mode built assets in the way, you will be seeing different results. Even if you disable live reloading entirely, you still aren't seeing CSS changes - even after restarting the server and hard-refreshing the browser, as you say. Which is what you are suggesting, right? This is actually a problem entirely separate from and unrelated to live-reloading. If so, this is unrelated to "live reloading", you wouldn't/aren't seeing changes even upon manually reloading. Which is why you don't see changes until you run assets:precompile again. So, once you've run that ONCE, these production-mode built assets are there, and the Rails app it just using them and ignoring the development-mode stuff. The only thing that's updating the CSS is running 'rails assets:precompile' Try /r/railsjobs, /r/forhire, or the following job sites: Looking for work, or need to hire Rails developers? Make sure the only reported file is the compiled css. But since the livereload client doesn't know this file then it will reload the whole page. (you have it globally, take in only in the css) Because of this it will trigger a livereload event for the scss file as well. Ruby Doc: Complete and accurate documentation for the Ruby programming language First of all don't enable livereload on for the compass task.When build my project & run it with dotnet run command after editing sass file nothing happens. Rails API: Searchable docs built with the sdoc gem. css get generated & scss styles doesn't works.APIdock: Rich and usable interface for searching, perusing and improving the documentation.Bundler: Manages an application's dependencies.Ruby Version Manager (RVM): alternative ruby environment manager.Rbenv: manage multiple ruby environments. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |