A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Home Page: https://webpack.js.org
License: MIT License
I haven't tried it yet, but does webpack reduce dependencies according to the package version? So if a module with the same version number is included from two different directories, e.g. A/node_modules/[email protected] and B/node_modules/[email protected], webpack should include it only once into the bundle.
It would be even better if webpack includes only one version as long as the major version of those two dependencies don't differ. So if myLib1 depends on [email protected] and myLib2 depends on [email protected], webpack should include only [email protected] because - according to semver - it won't break myLib2. Maybe this should be opt-in as it is potential risky.
In any case webpack should log a warning if two versions of the same module are included.
I'm not sure what the best solution for this is, but IDEs like Aptana Studio have a file indexer, installing a lot of modules slows down the build. Pretty annoying if you have to wait before you can do something else.
That's just partially webpack's problem, but it could still use some refinement.
webpacks tutorial tells you to install webpack locally and globally. Shouldn't it be just one of those? Would be nice if the user could choose between installing his dev environment separately (global) or bound to the project. The latter makes more sense at the moment, as webpack introduces some specific features, which binds one's project to webpack anyways.
Still, I would prefer a complete global install of webpack and it's modules.
For comparison, grunt installs globally, while it's plugins are installed locally. That at least, keeps that huge chunk of grunt main code out of the project, while plugins are small. That is, I think, because you can't put any modules in your package.json to be installed globally.
To sum up: I would like to see webpack being more loosely coupled to my project and satisfied with a global install. One build.json or webpack.js in the projects main should be sufficient.
For compatibility reasons modules-webpack's require should provide the same API as node's require. Especially the cache-object can be very useful (e.g. for unit tests).
Webpack become bigger than initially excepted (like many other growing projects ;) ), and the current design is not longer suitable for planed features...
So a important step must be a big refactoring to a better design!
This will also result in a API change, because the current API is weird in some aspects and many options are not logical named/ordered/categorized. (I'll offer a deprecated backward compatible API, will warnings as hints for migration)
It's cool that we have a good bunch of tests so that we can test the new design. I'll to add only a few new features with 0.9, but I'll prepare the design for source maps and hot code replacement. It would be good if we could share more code with enhanced-require.
I'll move some stuff out of enhanced-resolve to keep this library more reuseable.
This (API) stuff is weird and will be changed:
loaders option in the resolve object?postprocess is weird. OO-Solution: Extend a factory class.and this (internal) stuff:
I'll post more stuff on progress in the issue, so keep watching
Both 'mockery' and 'sandboxed-module' are unable to mock out modules that have been required with 'enhanced-require'. Please advise how to mock such modules.
Add support for Source Maps.
I really like TJ's approach of components. I haven't tried it yet but it would be cool if webpack was able to consume those components without hassle.
It's a good idea to write small components that are independent from big libraries or specific bundlers. In an application I may use webpack as a bundler because it has several useful features. But I don't want to write a small component that requires to use webpack as a bundler.
What do you think?
We could join the components-movement if webpack is able to consume components. Maybe TJ adds webpack as a recommendation.
When I'm not in debug mode the real module paths should not be included within require().
require(/* !/home/jhnns/webpack-test/app/pages/Main/MainPage.class.js */7);becomes
require(7);webpack's current error messages are not good readable. For example:
Error: the string "Cannot find module 'metaclass/lib/helpers/is.js'
Error: Module "metaclass/lib/helpers/is.js" not found in context "/media/sf_dev/nodeclass/lib"
Error: non in any path of paths
@ /media/sf_dev/nodeclass/lib/main.web.js (line 6, column 13)" was thrown, throw an Error :)
There seem to be several try-catch-blocks involved. But in this case it would be better if there is only one error, saying that module A required in module B can't be found in directory C.
3 error messages nested in one string are hard to understand.
I'm not quite sure how to handle these two variables. You haven't really documented this issue but after some testing I found out that you always pass ./index.js as filename and ./ as dirname.
I really like your approach of removing all the path resolution logic but I think for compatibility reasons you should also provide a file- and dirname (if requested). To accomplish this without leaking the real absolute path you could adopt the approach of browserify or webmake: All paths start from the top module root, e.g:
/jhnns/home/nodejs/myApp/app/someModule.js becomes /app/someModule.js/jhnns/home/nodejs/myApp/node_modules/someModule/lib/someOtherModule.js becomes /node_modules/someModule/lib/someOtherModule.jsnotes to self:
It seems like webpack is adding a superfluous comma at the end of the bundle. Although it's not valid JavaScript modern browsers are handling this error decently. But older browsers like IE7 fail.
/******/}, <----
/******/
/******/})
// END OF BUNDLEWhy do all source URLs start with webpack-module:// and than include the absolute file path? I think it would be more readable to just include the path after the module root. E.g. the file /home/jhnns/node/myModule/lib/printHello.js would appear as myModule/lib/printHello.js.
Currently I'm using Chrome to debug my scripts and it's kind of annoying to always resize the scripts panel to see how the actual filename is (because of the webpack-module prefix and the absolute path the string is quite long).
Despite of that, could you add to the readme that the debug option is also available when using the programmatic interface?
TBD
This would be a nice feature for the debug view. :)
Hi sokra,
could the "minimize with uglify.js"-option possibly be missing in the programmatical interface? I see you included it as a flag for the command line call, but it seems to be excluded from the json options object we could pass e.g. in our build.js, or at least it is not documented (and "min": true did not actually make my webpack output ugly ;))
Best regards,
Michael
I want to use EventEmitter2 from hij1nx. While in node context it works in browser context it is undefined.
Probably the last line of the module breaks webpack
;!function(exports, undefined) {
// ...
}(typeof process !== 'undefined' && typeof process.title !== 'undefined' && typeof exports !== 'undefined' ? exports : window);
Do you have any idea or solution how to solve this problem?
I want to use webpack to bundle unit tests in the test-folder. Therefore I want to search the test-folder for js-files and add these files to the bundle created by webpack. Is it possible to add multiple entry points like .addEntry() in browserify?
Many stuff is missing...
Many new stuff must be added for 0.9
I would appreciate it if a loader could define an own test-regexp to specify when it's called. This way a developer just has to apply the loader and don't care about the right regexp (or copy it from a readme file).
We're using for alamid's client tests nof5.
nof5 is basically a server which is able to use different bundlers, e.g. webpack, to bundle and serve client tests. One advantage of nof5 is that there is no need to write any tmp-file for the tests. So you won't have any problems with permissions.
So nof5 expects from the bundlers to be able to return a bundle as a string.
This is how webpack is implemented as bundler for nof5: WebpackBundler.
I wanted to updated the dependecy to webpack to version 0.6.x, but webpack isn't return a string any more.
Is there any possibility to get the bundle as string?
I haven't found the npm command in your readme to install the webpack so I've entered the github repository name into the npm registry. But there you can only find grunt-webpack, so I was assuming I need grunt to run the module. After some research I've read the npm instructions in your readme by coincidence.
It's very confusing that this module is called modules-webpack on github and you're installing it via npm install webpack. I think the best solution would be to rename the repository to webpack and make the npm installation instructions more obvious. In addition it's very common to have a chapter Installlation right after the short description. Even though this module seems to be designed for all CommonJS-modules, the nodejs use-case will be the most usual.
However, your module is very interesting! :) Currently I'm doing some evaluation to find out if it's useful for my company.
I'm not quite sure if I'm doing it wrong, but webpack uses the .js-file instead of the browser-compatible .web.js. This is my test setup:
// Creating bundle via API
var webpack = require("webpack");
webpack(__dirname + "/testEntry.js", {
output: __dirname + "/testBundle.js"
}, function onWebpackFinished(err, stats) {
if (err) throw err;
console.log(stats.fileModules["testBundle.js"]);
});// testEntry.js
var bla = require("./bla.js");// bla.js
module.exports = "bla";// bla.web.js
module.exports = "bla.web";[ { id: 0,
size: 81,
filename: '[...]/testEntry.js',
dirname: undefined,
fromCache: undefined,
toCache: undefined,
reasons: [ [Object] ] },
{ id: 1,
size: 69,
filename: '[...]/bla.js',
dirname: undefined,
fromCache: undefined,
toCache: undefined,
reasons: [ [Object] ] } ]
bla.js and bla.web.js are in the same folder. The error occurs on linux and windows. My current webpack version is 0.4.12. Any idea? :)
Hi @sokra
With a components directory that looks like this:
A.js
B.js
B.web.js
C.js
And my ComponentLoader that requires it like this:
var ComponentLoader = {
get: function(name) {
return require('../components/' + name);
},
available: function() {
var components = require.context('../components').keys();
return components.map(function(fileName) {
return fileName.replace('./', '').replace('.js', '');
});
}
};
It would be super cool if the context included only
A.js
B.web.js
C.js
in the browser, and
A.js
B.js
C.js
in node.
Currently the context includes all files in the browser and node. (And webpack throws a little error, because B.js includes net.)
I just wanted to install recent webpack version, but I got the following error:
Error: No compatible version found: webpack@'>=0.6.0- <0.7.0-'
npm ERR! Valid install targets:
npm ERR! ["0.1.0","0.1.1","0.1.2","0.1.3","0.1.4","0.1.5","0.1.6","0.2.0","0.2.1","0.2.2","0.2.3","0.2.4","0.2.6","0.2.7","0.2.8","0.3.0","0.3.1","0.3.2","0.3.3","0.3.4","0.3.6","0.3.7","0.3.8","0.3.9","0.3.10","0.3.11","0.3.12","0.3.13","0.3.14","0.3.15","0.3.16","0.3.17","0.3.18","0.3.19","0.3.20","0.4.0","0.4.1","0.4.2","0.4.3","0.4.4","0.4.5","0.4.6","0.4.7","0.4.8","0.4.9","0.4.10","0.4.11","0.4.12","0.4.13","0.4.14","0.4.15","0.4.16","0.4.17","0.4.18","0.4.19","0.4.20","0.4.21","0.4.23","0.4.24","0.4.25","0.5.0","0.5.1","0.5.2","0.5.3","0.5.4","0.5.5","0.5.6","0.5.7","0.5.8","0.5.10"]
I'm running node 0.8.7 and I've tested it also with 0.8.6.
Reloading the whole page on bundle update is ok, but a far time goal is to replace modules on runtime. (Idea from #25)
It's a far time goal, but it may be good to start discussion early...
Steps:
Goals:
Problems:
I had an issue today with bundling the validator node-module. I checked the package.json and the problem is how the main-file is referenced:
"main" : "./lib",
I changed it locally to lib/index.js and it works.
I think it's valid to reference main via path instead of a full-file-path, so webpack should resolve it the same way node does it.
And for testing with the validator module: Bundling the validator module doesn't work completely because it's referencing the native node-module "net". It removed this dep and it works completely.
The node-module path uses process.cwd() several times, but process.cwd() doesn't seem to be a function in the browser when I haven't passed a context via the options. Imho webpack should always assume a context when no one has been specified, maybe process.cwd().
If a loader decides to throw an error, I think it's better not to catch the error within webpack. A loader error is critical and should be reported immediately to the the developer.
Hi sokra,
when I try to build the following setup
project root
|__ lib
| |__ lib.js
|__ src
| |__ main.js
|__ build.js
with webpack 0.8.2, where lib.js is some arbitrary library and main.js is as simple as
// main.js
'use strict';
/*global require:true */
require = require('enhanced-require')(module, {
recursive: true
});
var Lib = require('../lib/lib.js');
then node build (i.e. basically a clone of your build script) would throw the following error:
ERROR: Cannot find module '../lib/lib.js'
Error: Error: Module "jshint" not found in context "<project root>\src"
Error: <project root>\node_modules\webpack\buildin\jshint-webpack-web-loader is not a directory
@ <project root>\src\main.js (line 8, column 14)
This sample works if lib.js is moved to src and the import in main.js is changed accordingly. By the way, it does not matter if require or enhanced-require is used.
Best regards,
miffels
They should share more code, but this should be extracted into another module. webpack should not depend von enhanced-require.
Secondary: if you use webpack in an enhanced-require context it should execute modules (val-loader) in this context.
Hi @sokra
I am unable to see error messages from jade loader.
I assume I need to set debug flag for the loader, how do I do this.
I am working with wpt and dev-server
thx,
Kavaro
Hi @sokra
Nice work on this. :)
One minor issue that is easy to fix: When I run webpack the hashbang #!/usr/bin/env node fails, since your editor saved it with \r\n.
The actual error: env: node\r: No such file or directory
If I open it with my editor, set the line endings to Unix and save it, it works fine. :) Please set your editor to use Unix line endings, too.
Apparently this can also be set with git: evocateur/yui-configger@ecdc0a1 But I think you'll still have to re-commit the bin/webpack file manually.
Thanks a lot!
Hey @sokra
I just hacked together this little module: (not related to components/components)
I am using the ComponentLoader.available() function to return every component, so I can use them in a user interface.
var ComponentLoader = {
get: function(name) {
return require('../components/' + name);
},
available: function() {
var components;
if (typeof window !== 'undefined') {
components = require.context('../components').keys();
} else {
components = require('fs').readdirSync('./components');
}
return components.map(function(fileName) {
return fileName.replace('./', '').replace('.js', '');
});
}
};
module.exports = ComponentLoader;
It works surprisingly well. My main grief points are the following:
process.browser or some other utility variable to tell us where our code is running?components = require.context('../components').keys(); in the browser and the server, but got the following error:Error:
TypeError: Object function () { [native code] } has no method 'keys'
at Object.ComponentLoader.available (/Users/rainerdreyer/Workspace/PipeDream/src/ComponentLoader.js:9:55)
at Object.<anonymous> (/Users/rainerdreyer/Workspace/PipeDream/main.js:12:45)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Object..js (/usr/local/lib/node_modules/node-dev/wrapper.js:121:15)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)
at require (module.js:378:17)
at Object.<anonymous> (/usr/local/lib/node_modules/node-dev/wrapper.js:177:1)
So is it possible to use the exact same code on both server and client?
Thanks!
I think there are some serious performance problems with webpack. Currently we're generating first bundles with alamid. The basic bundle (without application logic) contains about 50-60 modules. This is fine because we like modularity and prefer writing many short modules than a single long one.
Right now webpack takes about 2 secs (!) to compile the file. This is way too long. I don't know if you have any performance tests yet, but I think it is a good idea to spend some time on improving it. Maybe you can use flame graphs for it.
We (at alamid) surely haven't done everything right and could reduce some file system calls. But I think the main problem lies in webpack.
One performance gain could be achieved by replacing all asynchronous file system tasks to synchronous ones. Since you're not bundling for every HTTP-request in production it's a good idea to make it synchronous.
Hi @sokra
When I try to require('jquery'), which is a jam module installed under web_modules, I always get the following message:
- Serving static content.
- dev-server on port 8081.
> Open http://localhost:8081/ in your browser.
Error: watch ENOENT
at errnoException (fs.js:806:11)
at FSWatcher.start (fs.js:837:11)
at Object.fs.watch (fs.js:861:11)
at module.exports (/Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/webpack.js:223:23)
at Array.forEach (native)
at EventEmitter.<anonymous> (/Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/webpack.js:222:19)
at EventEmitter.emit (events.js:123:20)
at writingFinished (/Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/webpack.js:522:19)
at /Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/webpack.js:379:30
at buildTree (/Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/buildDeps.js:103:3)
Hash: 4732db73d220259503822d5a079cf898
Compile Time: 677ms
Chunks: 1
Modules: 6
Modules including duplicates: 6
Modules first chunk: 6
<id> <size> <filename>
dev.bundle.js
0 11 ./_template/entry.js [caching]
1 45 ./app/app.js [caching]
2 259828 ./app/web_modules/jquery/jquery.js [caching]
3 533 (webpack)/buildin/__webpack_amd_define.js [caching]
4 428 (webpack)/buildin/__webpack_amd_require.js [caching]
5 24 (webpack)/buildin/__webpack_options_amd.loader.js!(webpack)/buildin/__webpack_options_amd.loader.js [caching]
webpack: bundle is now VALID.
Jquery seems to be correctly bundled in the app and the server also works, but, I always get an error message related to watch and I am not sure whether it is save to ignore this message !!! For sure the message should not be there :-)
My setup as as follows:
wpt create jam-app
cd jam-app
npm install
Now add jam-dependencies to package.json
"jam": {
"packageDir": "app/web_modules",
"baseUrl": "app",
"dependencies": {
"jquery": "1.8.0",
"bootstrap": "2.1.1-jam.1"
}
},
Then run:
jam install
dev-server.sh
And now the error messages start to appear
Since version 0.5.10 webpack requires every loader in a new "context" by removing all modules from cache and readding them after the loader has been executed.
I think it's very delicate to mess around with require.cache because this can lead to totally unexpected behavior. Is there are an important reason why you've introduced this?
Currently I have to lock webpack at version 0.5.8 because it breaks my code.
Hey,
I'm trying to pack https://github.com/ded/klass and webpack isn't impressed with it:
> webpack node_modules/klass/klass.js klass.packed.js
Hash: 214a480310b53c1a2c79305e8fbc6cf7
Compile Time: 124ms
Chunks: 1
Modules: 1
Modules including duplicates: 1
Modules first chunk: 1
main klass.packed.js: 893 chars/bytes
<id> <size> <filename>
klass.packed.js
0 ./~/klass/klass.js
ERROR: Entry module failed!
Error: File "/Users/rainerdreyer/Workspace/PipeDream/node_modules/klass/klass.js" parsing failed: TypeError: Cannot call method 'push' of undefined
@ ./klass.js
But there is no call to push in the klass source code as far as I can see. Could you check why webpack can't handle this? Unfortunately most of my code uses inheritance with klass, so the packaging of everything fails.
Thanks!
Hi sokra,
yesterday I tried adding Backbone to one of my projects and ran into some issue I do not fully understand. My setup is webpack 0.7.8, Backbone 0.9.2 (both in web_modules and node_modules, installed locally via jam or npm respectively) and enhanced-require 0.4.0-beta3 running on node 0.8.11.
When I try to webpack a file with the following contents
'use strict';
require = require('enhanced-require')(module, {
recursive: true
});
var Backbone = require('backbone');
console.log(Backbone);
I get the following warning-error-mix:
<WARN> Cannot find module 'exports'
Error: Module "exports" not found in context "<project path>\web_modules\backbone"
Error: non in any path of paths
@ <project path>\web_modules\backbone\backbone.js (line 15, column 36) Use --force to continue. </WARN>
Since it is a mere warning, I could force the build though, giving me about what I expected in the console.log line. Nevertheless, did you ever face that warning? How can I get rid of it?
Interestingly enough, when I remove the jam version of Backbone, webpack runs without complaining about anything. Then again, there is only the Backbone namespace in the console.log output, i.e. it containts neither View, nor Model, nor any other object or function.
Best regards,
Michael
http://wiki.ecmascript.org/doku.php?id=harmony:specification_drafts
They should be packaged too.
import "jquery";
// => var __x__ = require(1), $ = __x__.$, jQuery = __x__.jQuery;
import $ from "jquery";
// => var __x__ = require(1), $ = __x__.$;
import { encrypt, decrypt } from "crypto"
// => var __x__ = require(2), encrypt = __x__.encrypt, decrypt = __x__.decrypt;
import { encrypt as enc } from "crypto"
// => var __x__ = require(2), enc = __x__.encrypt;
module "security" { }
// => var __WEBPACK_LOCAL_MODULE_1__ = {}; (function(exports) { }.call(this, __WEBPACK_LOCAL_MODULE_1__));
module crypto from "crypto";
// => var crypto = require(2);
export var document = 1234;
// => var document = 1234; exports.document = document;
export function parse() { };
// => function parse() { }; exports.parse = parse;
export default = 42;
// => module.exports = 42;
// => __WEBPACK_LOCAL_MODULE_1__ = 42;
export * from "crypto";
// => var __x__ = require(2); for(var name in __x__) exports[name] = __x__[name];
export { encrypt, decrypt as dec };
// => exports.encrypt = encrypt; exports.dec = decrypt;I think it would be nice to align the module-object as much as possible to node's module object although it's not too important for many modules (because most of the time you don't really need the module-object).
module.id could than be the module-id assigned by webpack.
I think it would be nice to just require an html file without having to use the raw-loader.
What do you think?
In the last issue you pointed out to use a postLoader like this:
module.exports = function(source) {
// do something
return source;
}Is the signature of pre- and postLoaders documented anywhere?
Hi sokra,
I just got involved in another JS project and decided to stick with the tools I am familiar with, i.e. webpack, among others. Unfortunately when I created a new project I ran into some strange errors I could not explain. I ended up cleaning my old project of all generated content (npm & jam modules) and updated the dependencies. Now with node-jquery 1.8.3 my old project won't build at all. When I try to webpack the following minimal example
// main.js
'use strict';
/*global require:true */
require = require('enhanced-require')(module, {
recursive: true
});
var $ = require('jquery');
I get the following warnings:
WARNING: A file in context was excluded because of error: Error: File "<project root>\node_modules\jquery\node_mod
ules\jsdom\lib\jsdom\level1\core.js" parsing failed: Error: Line 418: Unexpected token )
WARNING: A file in context was excluded because of error: Error: File "<project root>\node_modules\jquery\node_mod
ules\jsdom\lib\jsdom\level2\html.js" parsing failed: Error: Line 446: Unexpected token )
WARNING: Cannot find module 'node-htmlparser/lib/node-htmlparser'
Error: Module "node-htmlparser/lib/node-htmlparser" not found in context "<project root>\node_modules\jquery\node
_modules\jsdom\lib\jsdom\browser"
Error: <project root>\node_modules\webpack\buildin\node-htmlparser\lib\node-htmlparser is not a directory
@ <project root>\node_modules\jquery\node_modules\jsdom\lib\jsdom\browser\index.js (line 336, column 24)
WARNING: Cannot find module 'tls'
Error: Module "tls" not found in context "<project root>\node_modules\jquery\node_modules\jsdom\node_modules\requ
est"
Error: Non of this files exists: <project root>\node_modules\webpack\buildin\tls-webpack, <project root>
\node_modules\webpack\buildin\tls-webpack.webpack.js, <project root>
\node_modules\webpack\buildin\tls-webpack.web.js, <project root>\node_modules\webpack\buildin\tls-webpack.js
@ <project root>\node_modules\jquery\node_modules\jsdom\node_modules\request\main.js (line 44, column 8)
WARNING: A file in context was excluded because of error: Error: File "<project root>\node_modules\jquery\node_mod
ules\contextify\node_modules\bindings\README.md" parsing failed: Error: Line 2: Unexpected token ===
WARNING: Cannot find module 'https'
Error: Module "https" not found in context "<project root>\node_modules\jquery\node_modules\jsdom\node_modules\re
quest"
Error: Non of this files exists: <project root>\node_modules\webpack\buildin\https, <project root>
\node_modules\webpack\buildin\https.webpack.js, <project root>\node_module
s\webpack\buildin\https.web.js, <project root>\node_modules\webpack\buildin\https.js
@ <project root>\node_modules\jquery\node_modules\jsdom\node_modules\request\main.js (line 40, column 10)
plus a ton of errors like:
ERROR: Cannot find module '../../../lib/numeric'
Error: Error: Module "jshint" not found in context "<project root>\src\client\numeric"
Error: <project root>\node_modules\webpack\buildin\jshint-webpack-loader is not a directory
@ <project root>\src\client\numeric\LinearSolver.js (line 7, column 36)
ERROR: Cannot find module '../../../../lib/spin'
Error: Error: Module "jshint" not found in context "<project root>\src\client\view\recipe"
Error: <project root>\node_modules\webpack\buildin\jshint-webpack-loader is not a directory
@ <project root>\src\client\view\recipe\RecipeListView.js (line 9, column 11)
ERROR: Cannot find module 'fs'
Error: Module "fs" not found in context "<project root>\node_modules\jquery\node_modules\xmlhttprequest\lib"
Error: <project root>\node_modules\webpack\buildin\fs is not a directory
@ <project root>\node_modules\jquery\node_modules\xmlhttprequest\lib\XMLHttpRequest.js (line 16, column 9)
For this example I npm installed the latest versions of jquery, webpack, enhanced-require (node_modules) and jam installed jquery (web_modules). Do you happen to have an idea of what went wrong here?
Is there a way to allow a dynamic require, e.g. something like require(myPath);, without switching into implicit context?
I totally lost with 'options' part in README and cant find any examples.
At first -
"You can also save this options object in a JSON file and use it with the shell command"
but next (at README) code are invalid JSON (use function and e.t.c). I got error on copy-paste.
So, what I do - Iam write small (dual-faced - node and browser) widget and use in it lodash. Its big module and I need to load it in browser separately, with <script src="vendor/lodash.min.js"></script>. In my code I use _ = @_ ? require 'lodash'`
How I can told to webpack to exclude lodash from package?
This issue is related to the discussion in browserify's repository (browserify/browserify#174). I think webpack brings some interesting ideas but there are some problems left.
First of all I like the way that webpack prefers modules that end on .web.js. This makes it much more easy to swap between nodejs/client modules.
But to illustrate my problem I have to tell something about my plans. I'm currently working on a framework that makes it easy to write an application that runs on the server- and client-side. Therefore an intelligent module packager is very important.
To alleviate the development process I've introduced some naming conventions:
.client.js.server.jsI don't want to discuss about the postfixes. But I think it's necessary to have a server-only postfix to prevent the packager from "accidentally" including the server module that may contain sensitive data like passwords. In this case the packager should throw an error like "Hey, you're trying to include a module that you probably don't want to include".
So if I have a module that is amphibious, it's necessary to have three files. One .client.js, one .server.js and one module without postfix, that forwards to .server.js. Thus another module can require(moduleWithoutPostfix) and get the right module according to the current environment.
I don't like the superfluous module that just forwards to the server-module. It even gets more complicated if I have an object that provides attributes for both environments and attributes that are only present in a specific environment.
I really don't know if there is an easy and nice solution, but I wanted to raise the question here because generally I think it's the business of the packager to introduce a simple convention.
As webpack is getting more and more complex....
Somebody wants to do this?
The node module util uses Object.create in the inherit-function. But in IE8 and lower Object.create is not defined. Thus util requires a shim to work properly in these browsers.
Not all JavaScript 1.8.5 features available in Object.create can be emulated but for the purpose of inherit I think this one provided by the MDN will do it.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.