New blog domain: kula.blog

By K -
It's still work in progress but new posts will be published on  https://kula.blog/ Thanks to 11ty base blog RSS is working from the start so it should be easy to add to your reader if you still use any :) If now then I hope you can sign up to the newsletter where I'll be publishing new posts and interesting articles to it from time to time. Please use  kula.blog  from now on.
Post a Comment

Convenient Node Debugger Run by NPM

By K -

If you read installation instruction of node-inspector you would think that the only way to use it is to install it globally. Here I want to suggest embedding it in the project.

Installation:

$ npm install -g node-inspector
$ npm install node-inspector --devDependencies

After doing that, you need to add "debug" line to "scripts" part of package.json

"scripts": {
    "start": "node app.js",
    "debug": "./node_modules/.bin/node-debug app.js" }

And run it:

$ node-debug app.js
$ npm run debug


It has downsides, that is obvious, but in my opinion it has also big advantages. 

New person on the team does not need to follow long readme of global modules to install - and remember how all of them are supposed to be run. Another advantage is ignoring all the problems that you may have with sudo (needing it to install anything global). In my opinion it is also simpler and more convenient. All commands can be scripts starting with $ npm run *.

Of course it has some downsides as well. In case of many projects you would need to install and update the same module in every project. "NPM run debug" is yet another thing that must be stated in readme or being part of team culture as known part of every project to be most useful, and the last one: anyone using IDE will still need to install it even knowing they are not going to ever use it. 

If you like this idea, give it a try :)

Comments

Post a Comment

Comments:

Popular posts from this blog

How to use NPM packages from private repositories on bitbucket

By K -
Image
Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public npmjs.org but still want to have an ability to install them easily. After googling and experimenting I have found simple solution. First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important. Change example from below to: user - username PASS - password of the user organization - owner of the project (you can find it in bitbucket url to your project) project - your project name "de
Read more

How to simulate slow connection (developer proxy in Node.js)

By K -
Image
Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy. Toggle device mode   Choose Network type. Refresh the page https://developer.chrome.com/devtools/docs/device-mode  Proxy: For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me. I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one. https://github.com/nodejitsu/node-http-proxy With this module I can write really short code to create slow server: var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host:
Read more