Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"util.puts: Use console.log instead" issue #1529

Closed
slavafomin opened this issue Sep 6, 2013 · 3 comments
Closed

"util.puts: Use console.log instead" issue #1529

slavafomin opened this issue Sep 6, 2013 · 3 comments

Comments

@slavafomin
Copy link

Hello there!

When i run "lessc" command i'm getting some debug output all the time, see:

slava@destiny:~$ lessc --version
util.puts: Use console.log instead
lessc 1.4.2 (LESS Compiler) [JavaScript]

And all the resulted files (.less > .css) also include this line on top of them.

I'm running Xubuntu 13.04, installed LESS from with Node and NPM.

Please advise, thanks! )

@slavafomin
Copy link
Author

Update: Looks like it's a problem with NodeJS actually.

I've completely removed nodejs, npm and less packages from my system and installed it from chris-lea PPA:

Removing the stuff:
sudo npm remove -g less
sudo apt-get remove nodejs npm
sudo apt-get autoremove
sudo apt-get autoclean

Updating system:
sudo apt-get update
sudo apt-get dist-upgrade

Installing from scratch:
sudo add-apt-repository ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install nodejs
sudo npm install -g less

@lukeapage
Copy link
Member

yes, unless something has become deprecated I don't think this is a problem.

picomancer pushed a commit to picomancer/less.js that referenced this issue Sep 16, 2013
@picomancer
Copy link

unless something has become deprecated I don't think this is a problem

util.puts() / sys.puts() are in fact deprecated in Node. I reproduced the error messages with a vanilla install of the current node master branch (currently nodejs/node-v0.x-archive@59a075e).

The deprecation warnings have become more annoying over time, not sure whether this is accidental or on purpose. When I tested by compiling Node at the original commit that deprecated them (nodejs/node-v0.x-archive@896b2aa), the deprecation is only displayed once at the top of the output. But the current Node version shows the deprecation warning after every output line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants