How to compile Less locally on the fly ftp?

Question

css

I tried to compile on the server side , as a result, two less files in a row with @import did not want to work in any way. Began to look at compilation methods locally. Less2css sublime plugin. How to use it correctly for compilation in order to avoid such errors when editing a file in ftp (Transmit)?

FileError: '../global/variables.less' wasn't found in /Users/admin/Library/Caches/Cleanup At Startup/Transmit/1CEC5E30-8D69-43D9-9773-40BB3633658D/my.less on line 1, column 1:
1 @import "../global/variables";

Well, it is clear that he is trying to find a file locally to import variables, although he is on the server. How can it be taught to take variables from the server through the same ftp client? Or how do you do it?

Answer 1

There is such software PreprosApp . As far as I remember, it compiles locally less to css on the fly. Well, as for the server-side, tell the programmer to carefully read the documentation on the official LESS website, everything is described there.

Answer 2

Grunt.js is good

Answer 3

You can't compile locally what is only partially local.
The most optimal solution is to compile using server-side tools (php, node.js)? or on the client side (less.js).

Answer 4

- Download the entire project to the local machine, make changes, compile less (in an IDE or an external compiler) and upload to the server. Moreover, the IDE can upload only changed files (less and final css)
- Run a server-side compiler that would track changes in less files and compile into final css. You only need 1 changeable less to download and upload.
- Compile less in the browser, but then the load on the client will increase, and if you have a lot of js there or a mobile device, then the extra load is not needed.

Answer 5

You need to put node.js and LESS on the local machine. And calmly compile your CSS.
Everything else, including less.js - IMHO, a perversion.
In general, I recommend using SASS (SCSS) instead.

Answer 6

Why cloning?
Take a new HDD, divide it into two partitions, copy important information from the old HDD to one, put windows on the other partition.
If the old HDD is no longer readable, perform similar actions from another PC on the new HDD - divide into sections, move all the necessary information to one of the partitions, format the second and install windows.

Answer 7

The problem is solved through a mega-crutch.
The system was rolled back to 8.1, the boot was restored, cloned to a new screw and updated to win10 on a new screw.