Posted: May 5th, 2012 | Author: lukas | Filed under: meteorjs, Ubuntu | Tags: meteorjs, nodejs | No Comments »I got following error when tried to use node.js package (installed with npm) in meteorjs application on my Ubuntu:
node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead.
You can find sample code causing error here.
I’ve tried setting NODE_PATH in bash but with no success.
Then I’ve looked into meteor script (under /usr/bin) and saw that meteor is setting NODE_PATH by itself (it is pointing to /usr/lib/meteor/lib/node_modules directory). I cloned required package directly from github into /usr/lib/meteor/lib/node_modules directory and my application run wihout any errors.
Posted: September 17th, 2010 | Author: lukas | Filed under: Rails | Tags: rails, sqlite, windows | No Comments »After successfully installed Rails I’ve created clean project using
rails new helloworld_project
command and installed sqlite3 gem.
Read the rest of this entry »
Posted: September 17th, 2010 | Author: lukas | Filed under: Rails | Tags: gem, proxy, rails, windows | No Comments »Lately I’ve changed computer to new one and I’ve lost my Rails installation. Today I decided to recreate my environment. My computer is behind a HTTP proxy so I’ve knew that I will have some problems with installing Rails using gem installer.
Read the rest of this entry »
Posted: March 25th, 2010 | Author: lukas | Filed under: Java | Tags: Google App Engine, Java, JSF | 6 Comments »Some time ago I decided to familiarize with Google App Engine capabilities. Lately I read a document about GAE Java SDK version capabilities. I was surprised that a big part of JEE stack is supported e.g.: JPA and JSF. That moment I decided to make simple JSF-based demo application.
Read the rest of this entry »
Posted: March 15th, 2010 | Author: lukas | Filed under: Java | Tags: EclipseLink, Java, logging, SLF4J | No Comments »I’m using EclipseLink as JPA provider in some of my OSGi based projects. Latelly I also switched from Apache Commons Logging to SLF4J (shortly speaking not to be forced to write LOG.isDebugEnabled() in case of debug messages in my code). Then I found out, that EclipseLink is using it’s own logger which can not be configured using standard log4j.xml file.
Read the rest of this entry »
