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

Semantic Versioning

By K -
Idea is not new, similar approach can be found in many places but now it has nice name.

Lately I read Node Web Development and Node.js modules in npm used this approach to make npm so awesome.

Read more at website: http://semver.org/

In a brief:

  1. There is API, it can be code or whatever but this is treated like API.
  2. Use 3 numbers: 1.2.3 - <major>.<minor>.<patch>
  3. Patch - bugifex - API comatible
  4. Minor - new or compatible API changes
  5. Major - any incompatible API changes
How this can help?
By using "strict" convention this can be used by tools (like npm) to make it easier to You to update dependencies. If You use library in version 1.2.0, then You can update easily it up to 2.0.0! Of course it is better co confirm it by developer that this really works, but if library developer uses semver like You, it should!

There are many other rules, if You can't use it, at leas show it to You's co-workers, it would be great to really standardize this, at low level. 

But I am curious, if I have common module that gets data from DB, and displays it on page... What changes are compatible? If only users use this html code, all changes are compatible, or incompatible...
Maybe semver is just for libraries, not front-end staff like html?
For xml/json it is easier, there is only data. 
Html has also id's and classes, there is CSS and JavaScript that are tight coupled. 


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