<commit_before># modules-webmake

_Bundle CommonJS/Node.js modules for web browsers._

__Webmake allows you to organize JavaScript code for the browser the same way as you do for Node.js.__

Thanks to that, you can work with best dependency management system that JavaScript currently has, and easily, without extra boilerplate, reuse your modules in any environment that runs JavaScript _(server, client (any web browser), other custom stuff as e.g. Adobe Photoshop, or even your dishwasher if it speaks JavaScript)_.

It additionally natively supports __CSS__ and __HTML__ files, which makes it a full stack modules bundler for a web browser.

<img src="http://medyk.org/webmake.png" />

Files support can be extended to any other format that compiles to one of _.js_, _.json_, _.css_ or _.html_. See __[custom extensions](#extensions)__ for more information.

For a more in depth look into JavaScript modules and the reason for _Webmake_,
see the slides from my presentation at Warsaw's MeetJS: [__JavaScript Modules Done Right__][slides]

___If you wonder how Webmake compares with other solutions, see dedicated [comparison section](#comparison-with-other-solutions)___

## How does dependency resolution work?

As it has been stated, Webmake completely follows Node.js in that

Let's say in package named _foo_ you have following individual module files:<commit_msg>Force update of image by Github<commit_after># modules-webmake

_Bundle CommonJS/Node.js modules for web browsers._

__Webmake allows you to organize JavaScript code for the browser the same way as you do for Node.js.__

Thanks to that, you can work with best dependency management system that JavaScript currently has, and easily, without extra boilerplate, reuse your modules in any environment that runs JavaScript _(server, client (any web browser), other custom stuff as e.g. Adobe Photoshop, or even your dishwasher if it speaks JavaScript)_.

It additionally natively supports __CSS__ and __HTML__ files, which makes it a full stack modules bundler for a web browser.

<img src="http://medyk.org/webmake.copy.png" />

Files support can be extended to any other format that compiles to one of _.js_, _.json_, _.css_ or _.html_. See __[custom extensions](#extensions)__ for more information.

For a more in depth look into JavaScript modules and the reason for _Webmake_,
see the slides from my presentation at Warsaw's MeetJS: [__JavaScript Modules Done Right__][slides]

___If you wonder how Webmake compares with other solutions, see dedicated [comparison section](#comparison-with-other-solutions)___

## How does dependency resolution work?

As it has been stated, Webmake completely follows Node.js in that

Let's say in package named _foo_ you have following individual module files:
{'fraction_non_alphanumeric': 0.05384893386338995, 'fraction_numerical': 0.0, 'mean_word_length': 4.978401727861771, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '390112', 'n_tokens_mistral': 707, 'n_tokens_neox': 682, 'n_words': 384}