I have many colleagues and friends with existing brown fields, dirty javascript applications who would like to start the transition to some kind of modular js system. I tried to help them in the past by showing them how to reorganize on requirejs, but I'm starting to think that this is a bad approach.
Usually the problem is that the nature of their globally collaborative code contradicts the asynchronous nature of AMD and, as far as I think, AMD’s approach, they have more problems than in my lectures on the “correct” way to load a module.
Browserify, meanwhile, removes asynchronous browsing and is simpler, but adds a whole build step. For people who do not use binding or any kind of build process (or just the default in visual studio), this again is too much overhead.
So what I really want is a simple module system that allows people to define and require things. This is a half-step step towards proper functioning; they can include their dependencies with regular script tags and define them manually in the module system. I even wrote such a system because ... hey, it's very simple.
Today, someone pointed out to me that for this you only need to use parts of the Browserify browser on the client side. I agree. However, I can not find any documentation anywhere and not just a browser client side browser.
javascript client-side browserify
George mauer
source share