Modern practice for client side javascript source structure with CommonJS TypeScript etc -


my javascript foo okay haven't kept latest , greatest (we don't use node.js in backend).

what modern practice of structuring client side javascript?

we organize javascript in sub directories smaller files, , minify , concatenate them production.

when check these popular client side js libraries

https://github.com/mbostock/d3

https://github.com/jquery/jquery

https://github.com/chriszarate/supergenpass

they not written in client side javascript @ , seems alien me.

it seems nowadays have learn commonjs , slew of frameworks comprehend , contribute.

i tried googling around returns list of server side node.js related hits (grunt) none talks using maintain client side library.

any pointers?

so i've been doing more research. seems answer in commonjs , node.js

some client side frameworks use commonjs break code modules (which browsers won't understand), , use node.js , package manager bowsify combine these modules single javascript file.


Comments

Post a Comment

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

im trying write component admin side , need add user creation. dont want duplicate existing codes add link. know how add task not simple link toolbar. thx help. if wanting button opens new user screen can try in component: $bar = jtoolbar::getinstance('toolbar'); $bar->appendbutton('link', 'users', 'new user','index.php?option=com_users&task=user.add'); you need add view.html.php file wherever you're creating toolbar. is need?
Read more

linux - disk space limitation when creating war file -

i have 1 gb disk space limitation hosting app , have used 700mb of it. however want create war file directory big (around 600mb) using command : jar -cvf root.war folderpath that's why encounter quota limitation , can't following. i'm looking way delete folder content when it's applying archive conserve disk space take note can't install zip tool in ssh shell ~ the code works on test directories, test first anyway, deletes files. it's not efficient. assumptions: 300mb free space, in destructively compress 600mb folderpath directory. none of files big -- if file in folderpath 300mb or larger, fail. notes: if ' $out ' file exists, nothing. first find pipes file list while , if ' $out ' doesn't exist in loop, create it, don't update -- if does exist, update it. each pass adds 1 more file, deletes unless file directory. after loop finishes delete empty directories too. unset u ; in=folderpath ; out=roo...
Read more