In PHP:

- When should I use `require` vs. `include`?
- When should I use `require_once` vs. `include_once`?


Difference between require, include, require_once and include_once?

My question is similar to &quot;[What is the difference between include and extend in Ruby?][1]&quot;.

What&#39;s the difference between `require` and `include` in Ruby?  If I just want to use the methods from a module in my class, should I `require` it or `include` it?


  [1]: https://stackoverflow.com/questions/156362/what-is-the-difference-between-include-and-extend-in-ruby

What is the difference between include and require in Ruby?

I&#39;ve just started working on a small node project that will interface with a MongoDB. However, I cannot seem to get the relevant node modules to import correctly, even though I have installed them correctly via `npm`.

For example, the following code throws an error, telling me that &quot;express has no default export&quot;:

    import express from &quot;express&quot;;

However, this code works:

    const express = require(&quot;express&quot;);

**So my question is, what is the difference in how the import and variable/require methods function?** I&#39;d like to fix whatever is plaguing my imports on the project, as it seems likely to cause additional problems down the road.

The difference between &quot;require(x)&quot; and &quot;import x&quot;

What&#39;s the best way to require all files from a directory in ruby ?

Best way to require all files from a directory in ruby?

How can I detect whether my Node.JS file was called using SH:`node path-to-file` or JS:`require(&#39;path-to-file&#39;)`?

This is the Node.JS equivalent to my previous question in Perl: https://stackoverflow.com/questions/4004466/how-can-i-run-my-perl-script-only-if-it-wasnt-loaded-with-require

Detect if called through require or directly by command line

I would like to include a couple of JSON files in my JavaScript code that are in the same directory as my JavaScript source file.

If I wanted to include another JavaScript file I could simply use `require`.
Now I&#39;m using `readFileSync` and `__dirname` to get the JSON, which I think is an ugly way to do it.

Is there something similar for require that enables me to load a JSON file?


is there a require for json in node.js

What is the difference between `require_relative` and `require` in Ruby?

What is the difference between require_relative and require in Ruby?

I have being playing around with requirejs for the last few days.  I am trying to understand the differences between define and require.

Define seems to allow for module separation and allow for dependency ordering to be adhere.  But it downloads all the files it needs to begin with.  Whilst require only loads what you need when you need it.

Can these two be used together and for what purposes should each of them be used?

When should I use require() and when to use define()?

I would like to require my files always by the root of my project and not relative to the current module.

For example if you look at https://github.com/visionmedia/express/blob/2820f2227de0229c5d7f28009aa432f9f3a7b5f9/examples/downloads/app.js line 6 you will see

    express = require(&#39;../../&#39;)

That&#39;s really bad IMO. Imagine I would like to put all my examples closer to the root only by one level. That would be impossible, because I would have to update more than 30 examples and many times within each example. To this:

    express = require(&#39;../&#39;)

My solution would be to have a special case for root based: if a string starts with an $ then it&#39;s relative to the root folder of the project.

Any help is appreciated, thanks


# Update 2

Now I&#39;m using require.js which allows you to write in one way and works both on client and on server. Require.js also allows you to create custom paths.

# Update 3

Now I moved to webpack + gulp and I use enhanced-require to handle modules on the server side. See here the rationale: http://hackhat.com/p/110/module-loader-webpack-vs-requirejs-vs-browserify/

How to make node.js require absolute? (instead of relative)

I am learning nodejs at the moment on Windows. Several modules are installed globally with npm.cmd, and nodejs failed to find the installed modules. Take jade for example,

    npm install jade -g

Jade is installed in directory `&quot;C:\Program Files (x86)\nodejs\node_modules&quot;`, but the following code will fail with a `&quot;Cannot find module &#39;jade&#39;&quot;` error,

    var jade = require(&#39;jade&#39;);

However, the code will run successfully when jade is locally installed (without -g option in npm). I don&#39;t want to use locally-installed modules, it&#39;s a waste of disk space for me. How can I make the globally-installed modules work on Windows?

Nodejs cannot find installed module on Windows

In PHP scripts, whether calling `include()`, `require()`, `fopen()`, or their derivatives such as `include_once`, `require_once`, or even, `move_uploaded_file()`, one often runs into an error or warning: 

&gt;Failed to open stream : No such file or directory.

What is a good process to quickly find the root cause of the problem?

PHP - Failed to open stream : No such file or directory

I&#39;ve been working with nodejs lately and still getting to grips with the module system so apologies if this is an obvious question. I want code roughly like the following below:

**a.js** (the main file run with node)

    var ClassB = require(&quot;./b&quot;);

    var ClassA = function() {
        this.thing = new ClassB();
        this.property = 5;
    }

    var a = new ClassA();

    module.exports = a;


**b.js**

    var a = require(&quot;./a&quot;);

    var ClassB = function() {
    }

    ClassB.prototype.doSomethingLater() {
        util.log(a.property);
    }

    module.exports = ClassB;


My problem seems to be that I can&#39;t access the instance of ClassA from within an instance of ClassB.

Is there a correct / better way to structure modules to achieve what I want?
Is there a better way to share variables between modules?

How to deal with cyclic dependencies in Node.js

I&#39;ve one file, main.rb with the following content:

    require &quot;tokenizer.rb&quot;

The tokenizer.rb file is in the *same directory* and its content is:

    class Tokenizer
    	def self.tokenize(string)
    		return string.split(&quot; &quot;)
    	end
    end

If i try to run main.rb I get the following error:


    C:\Documents and Settings\my\src\folder&gt;ruby main.rb
    
    C:/Ruby193/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require&#39;: cannot load such file -- tokenizer.rb (LoadError)
            from C:/Ruby193/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require &#39;
            from main.rb:1:in `&lt;main&gt;&#39;

I just noticed that if I use `load` instead of `require` everything works fine. What may the problem be here?

Ruby &#39;require&#39; error: cannot load such file

Is there any difference between them? Is using them a matter of preference? Does using one over the other produce any advantages? Which is better for security?

Difference between &quot;include&quot; and &quot;require&quot; in php

I&#39;m building a node app, and inside each file in .js used to doing this to require in various packages.

    let co = require(&quot;co&quot;);

But getting 

[![enter image description here][1]][1]

etc. So using typescript it seems there can only be one such declaration/require across the whole project? 
I&#39;m confused about this as I thought `let` was scoped to the current file.

I just had a project that was working but after a refactor am now getting these errors all over the place.

Can someone explain?


  [1]: http://i.stack.imgur.com/Dgrz2.png

Cannot redeclare block scoped variable

As some of you may know, Google Chrome has put some severe limitation on Greasemonkey scripts.

&gt; Chromium does not support `@require`, `@resource`, `unsafeWindow`, `GM_registerMenuCommand`, `GM_setValue`, or `GM_getValue`.

Without require, I can&#39;t find a way to include the jQuery library in Greasemonkey script under Google Chrome. 

Does anybody have some advice in this matter? 

How can I use jQuery in Greasemonkey scripts in Google Chrome?

The latest changesets to Ruby 1.9.2 no longer make the current directory `.` part of your `LOAD_PATH`. I have a non-trivial number of Rakefiles that assume that `.` is part of the `LOAD_PATH`, so this broke them (they reported &quot;no such file to load&quot; for all require statements that based off the project path). Was there a particular justification for doing this?

As for a fix, adding `$: &lt;&lt; &quot;.&quot;` everywhere works, but seems incredibly hacky and I don&#39;t want to do that. What&#39;s the preferred way to make my Rakefiles 1.9.2+ compatible?

Why does Ruby 1.9.2 remove &quot;.&quot; from LOAD_PATH, and what&#39;s the alternative?

I&#39;m using node + express and I am just wondering how I can import any file as a string. Lets say I have a txt file all I want is to load it into a variable as such.

    var string = require(&quot;words.txt&quot;);

I am against 

    modules.exports = function(){
    
        var string = &quot;whatever&quot;;
        
        return string;

    }

require file as string

I am trying to require a file and afterwards pass it to a var. I am following [this](https://scotch.io/tutorials/easy-node-authentication-setup-and-local) tutorial to create an authentication system. After writing the server.js file and trying to compile I got a BSON error therefore I changed the line that required the release version of it in mongoose.

Here are my code and error: 

***server.js***

    require(&#39;./app/routes&#39;)(app, passport);

***Error***

    require(&#39;./app/routes&#39;)(app, passport);
                       ^

    TypeError: require(...) is not a function
               at Object.&lt;anonymous&gt; (d:\Node JS learning\WorkWarV2\server.js:38:24)
               at Module._compile (module.js:434:26)
               at Object.Module._extensions..js (module.js:452:10)
               at Module.load (module.js:355:32)
               at Function.Module._load (module.js:310:12)
               at Function.Module.runMain (module.js:475:10)
               at startup (node.js:117:18)
               at node.js:951:3

    Process finished with exit code 1

I have read that this usually means that `requireJS` is not getting loaded properly yet I am not aware why or how to fix it.

***Edit due to comment:***

As asked, [here](http://paste.isomorphis.me/vj3) is the result of `console.log(require);`

NodeJs : TypeError: require(...) is not a function

I have some things for development - e.g mocks which I would like to not bloat my distributed build file with.

In RequireJS you can pass a config in a plugin file and conditonally require things in based on that.

For webpack there doesn&#39;t seem to be a way of doing this. Firstly to create a runtime config for an environment I have used [resolve.alias][1] to repoint a require depending on the environment, e.g:

    // All settings.
    var all = {
    	fish: &#39;salmon&#39;
    };
    
    // `envsettings` is an alias resolved at build time.
    module.exports = Object.assign(all, require(&#39;envsettings&#39;));

Then when creating the webpack config I can dynamically assign which file `envsettings` points to (i.e. `webpackConfig.resolve.alias.envsettings = &#39;./&#39; + env`).

However I would like to do something like:

    if (settings.mock) {
    	// Short-circuit ajax calls.
    	// Require in all the mock modules.
    }

But obviously I don&#39;t want to build in those mock files if the environment isn&#39;t mock.

I could possibly manually repoint all those requires to a stub file using resolve.alias again - but is there a way that feels less hacky?

Any ideas how I can do that? Thanks.

  [1]: http://webpack.github.io/docs/configuration.html#resolve-alias

Conditional build based on environment using Webpack

Are there any libraries for in-browser javascript that provide the same flexibility/modularity/ease of use as Node&#39;s `require`?

To provide more detail: the reason `require` is so good is that it:

1.  Allows code to be dynamically loaded from other locations (which is stylistically better, in my opinion, than linking all your code in the HTML)
2.  It provides a consistent interface for building modules
3.  It is easy for modules to depend on other modules (so I could write, for instance, an API that requires jQuery so I can use `jQuery.ajax()`
4.  Loaded javascript is _scoped_, meaning I could load with `var dsp = require(&quot;dsp.js&quot;);` and I would be able to access `dsp.FFT`, which wouldn&#39;t interfere with my local `var FFT`

I have yet to find a library that does this effectively.  The workarounds I tend to use are:

-  [coffeescript-concat][1] -- it&#39;s easy enough to require other js, but you have to compile it, which means it is less great for fast development (e.g. building APIs in-test)

-  [RequireJS][2] -- It&#39;s popular, straightforward, and solves 1-3, but lack of scoping is a real deal-breaker (I believe [head.js][3] is similar in that it lacks scoping, though I&#39;ve never had any occasion to use it.  Similarly, [LABjs][4] can load and `.wait()` does mollify dependency issues, but it still doesn&#39;t do scoping)

As far as I can tell, there appear to be many solutions for dynamic and/or async loading of javascript, but they tend to have the same scoping issues as just loading the js from HTML.  More than anything else, I would like a way to load javascript that does not pollute the global namespace at all, but still allows me to load and use libraries (just as node&#39;s require does).

__2020 UPDATE:__ [Modules][7] are now standard in ES6, and as of mid-2020 are natively supported by [most browsers][8]. Modules support both synchronous and asynchronous (using Promise) loading. My current recommendation is that most new projects should use ES6 modules, and use a transpiler to fall back to a single JS file for legacy browsers.

As a general principle, bandwidth today is also typically much wider than when I originally asked this question. So in practice, you might reasonably chose to always use a transpiler with ES6 modules, and focus your effort on code efficiency rather than network.

__PREVIOUS EDIT (or if you don&#39;t like ES6 modules):__ Since writing this, I have extensively used [RequireJS][5] (which now has much clearer documentation). RequireJS really was the right choice in my opinion. I&#39;d like to clarify how the system works for people who are as confused as I was:

You can use `require` in everyday development. A module can be anything returned by a function (typically an object or a function) and is scoped as a parameter. You can also compile your project into a single file for deployment using `r.js` (in practice this is almost always faster, even though `require` can load scripts in parallel).

The primary difference between RequireJS and node-style require like browserify (a cool project suggested by tjameson) uses is the way modules are designed and required:

- RequireJS uses AMD (Async Module Definition). In AMD, `require` takes a list of modules (javascript files) to load and a callback function. When it has loaded each of the modules, it calls the callback with each module as a parameter to the callback. Thus it&#39;s truly asynchronous and therefore well-suited to the web.
- Node uses CommonJS. In CommonJS, `require` is a blocking call that loads a module and returns it as an object. This works fine for Node because files are read off the filesystem, which is fast enough, but works poorly on the web because loading files synchronously can take much longer.

In practice, many developers have used Node (and therefore CommonJS) before they ever see AMD. In addition, many libraries/modules are written for CommonJS (by adding things to an `exports` object) rather than for AMD (by returning the module from the `define` function). Therefore, lots of Node-turned-web developers want to use CommonJS libraries on the web. This is possible, since loading from a `&lt;script&gt;` tag is blocking. Solutions like browserify take CommonJS (Node) modules and wrap them up so you can include them with script tags.

Therefore, if you are developing your own multi-file project for the web, I strongly recommend RequireJS, since it is truly a module system for the web (though in fair disclosure, I find AMD much more natural than CommonJS). Recently, the distinction has become less important, since RequireJS now allows you to essentially use CommonJS syntax. Additionally, RequireJS can be used to load AMD modules in Node (though I prefer [node-amd-loader][6]).


  [1]: https://github.com/fairfieldt/coffeescript-concat
  [2]: http://requirejs.org/
  [3]: http://headjs.com/
  [4]: http://labjs.com/
  [5]: http://requirejs.org/
  [6]: https://github.com/ajaxorg/node-amd-loader
  [7]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules
  [8]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules#Browser_support

Node-style require for in-browser javascript?

When I do:

    lib = require(&#39;lib.js&#39;)(app)

is `app` actually geting passed in?

in lib.js:

    exports = module.exports = function(app){}

Seems like no, since when I try to do more than just `(app)` and instead do:

    lib = require(&#39;lib.js&#39;)(app, param2)

And:

    exports = module.exports = function(app, param2){}

I don&#39;t get `params2`.

I&#39;ve tried to debug by doing:

    params = {}
    params.app = app
    params.param2 = &quot;test&quot;
    
    lib = require(&quot;lib.js&quot;)(params)

but in lib.js when I try to `JSON.stringify` I get this error:

    &quot;DEBUG: TypeError: Converting circular structure to JSON&quot;








Node.js &quot;require&quot; function and parameters

I am using requireJS 2.x. I found out that some tutorials (and the official docs) sometimes use 

    requirejs.config({ [...] });
    requirejs([&quot;module&quot;]) ...

and sometimes

    require.config({ [...] });
    require([&quot;module&quot;]) ...

Is there any difference between those two functions (require and requirejs)? I could not find any word about that in the docs. :(

RequireJS: Difference between &quot;requirejs&quot; and &quot;require&quot; functions

I tried this:

    // mod.js
    var a = 1;
    this.b = 2;
    exports.c = 3;

    // test.js
    var mod = require(&#39;./mod.js&#39;);
    console.log(mod.a);    // undefined
    console.log(mod.b);    // 2
    console.log(mod.c);    // 3, so this === exports?

So I image that require() may be implement like this:

    var require = function (file) {
        var exports = {};
        var run = function (file) {
            // include &quot;file&quot; here and run
        };
        run.apply(exports, [file]);
        return exports;
    }

Is that right? Please help me to understand require(), or where can I find the source code. Thanks!

How does require() in node.js work?

I&#39;m developing a website with webpack. When I have a code like this:

    import $ from &#39;jquery&#39;;
    function foo() {};
    module.exports = foo;

I got the error `Uncaught TypeError: Cannot assign to read only property &#39;exports&#39; of object &#39;#&lt;Object&gt;&#39;`.

Turns out that changing `import $ from &#39;jquery&#39;` to `var $ = require(&#39;jquery&#39;)` don&#39;t cause any errors.

**Why import with module.exports causes this error? Is anything wrong in using require instead?**

webpack: import + module.exports in the same module caused error

I had initially been using electron stable (4.x.x), and was able to use `require` in both my browser and renderer processes. I upgraded to electron beta (5.0.0) because I needed a newer version of node and encountered this error message in my renderer process, `Uncaught ReferenceError: require is not defined`. 

Googling and looking through the electron docs, I found comments saying the error could be caused by setting `webPreferences.nodeIntegration` to false when initializing the `BrowserWindow`; e.g.: `new BrowserWindow({width, height, webPreferences: {nodeIntegration: false}});`. But I was not doing this, so I thought something else must be the issue and continued searching for a resolution.

electron 5.0.0 &quot;Uncaught ReferenceError: require is not defined&quot;

**How are `require` and `require_dependency` different?**  
How can `require_dependency` automatically reload classes in development but `require` can&#39;t ?

I digged into Rails&#39; `ActiveSupport::Dependencies` and dispatcher.rb code. What I saw in `require_dependency`&#39;s code is it basically adds the constants to an `autoloaded_constants` array. But it gets cleared in `clear_application` inside dispatcher after each request.

Can someone give a clear explanation or point me to some resources which will help?

How are require, require_dependency and constants reloading related in Rails?

I am having issues including files to execute in my NodeJs project.

I have two files in the same directory:

**a.js**

    var test = &quot;Hello World&quot;;

and 

**b.js**

    require(&#39;./a.js&#39;);
    console.log(test);


I execute b.js with `node b.js` and get the error `ReferenceError: test is not defined`.

I have looked through the docs http://nodejs.org/api/modules.html#modules_file_modules

What am I missing? Thanks in advance.

NodeJs require(&#39;./file.js&#39;) issues

Let say, after I require a module and do something as below:

    var b = require(&#39;./b.js&#39;);
    --- do something with b ---

Then I want to take away module b (i.e. clean up the cache).  how I can do it?

The reason is that I want to dynamically load/ remove or update the module without restarting node server.  any idea?


------- more --------
based on the suggestion to delete require.cache, it still doesn&#39;t work...

    what I did are few things:
    1) delete require.cache[require.resolve(&#39;./b.js&#39;)];
    2) loop for every require.cache&#39;s children and remove any child who is b.js
    3) delete b

However, when i call b, it is still there!   it is still accessible. unless I do that:

    b = {};

not sure if it is a good way to handle that. 
because if later, I require (&#39;./b.js&#39;) again while b.js has been modified.  Will it require the old cached b.js (which I tried to delete), or the new one?



----------- More finding --------------

ok. i do more testing and playing around with the code.. here is what I found:

    1) delete require.cache[]  is essential.  Only if it is deleted, 
     then the next time I load a new b.js will take effect.
    2) looping through require.cache[] and delete any entry in the 
     children with the full filename of b.js doesn&#39;t take any effect.  i.e.
    u can delete or leave it.  However, I&#39;m unsure if there is any side
    effect.  I think it is a good idea to keep it clean and delete it if
    there is no performance impact.
    3) of course, assign b={} doesn&#39;t really necessary, but i think it is 
     useful to also keep it clean.

  



How to remove module after &quot;require&quot; in node.js?

How would I require() a file if I had the file&#39;s contents as a string in memory, without writing it out to disk? Here&#39;s an example:

    // Load the file as a string
    var strFileContents = fs.readFileSync( &quot;./myUnalteredModule.js&quot;, &#39;utf8&#39; );
    
    // Do some stuff to the files contents
    strFileContents[532] = &#39;6&#39;;

    // Load it as a node module (how would I do this?)
    var loadedModule = require( doMagic(strFileContents) );

Load node.js module from string in memory

By using `require(./filename)` I can include and execute the code inside *filename* without any export defined inside *filename* itself.

What is the equivalent in ES6 using `import` ?

Thanks

ES6 import equivalent of require() without exports

Here is the project structure:

    /
      app.js
      package.json
      /node_modules
      /app
        config.json
        /frontend
          assets and html tpls
        /modules
          couch.js
          raeume.js
          users.js

I require config.json, raeume.js and users.js from app.js and it all works fine.

    var config   = require(&#39;./app/config&#39;);
    var raeume   = require(&#39;./app/modules/raeume&#39;);
    var users    = require(&#39;./app/modules/users&#39;);

Then I require config.json and couch.js from user.js the same way and it won&#39;t find anything.

    var couch     = require(&#39;./app/modules/couch&#39;);
    var config    = require(&#39;./app/config&#39;);

I guess it should find it. After some research I saw a diverse landscape of problems inclusive how node is compiled. Thus included: I work on osx 10.8 with node v0.10.7.

node.js require cannot find custom module

In Ruby, I have been told that when doing

    require &quot;some_file&quot;

Ruby will look for the file in certain places.

I know that it looks for `some_file.rb`, but where does it look for it by default?
    

What are the paths that &quot;require&quot; looks up by default?

I am writing some Ruby code, not Rails, and I need to handle something like this:

    found 1 match
    found 2 matches

I have Rails installed so maybe I might be able to add a `require` clause at the top of the script, but does anyone know of a RUBY method that pluralizes strings? Is there a class I can require that can deal with this if the script isn&#39;t Rails but I have Rails installed?

**Edit:** All of these answers were close but I checked off the one that got it working for me.
Try this method as a helper when writing Ruby, not Rails, code:

    def pluralize(number, text)
      return text.pluralize if number != 1
      text
    end


Is there a pluralize  function in Ruby NOT Rails?

Is there a shorter way to require a file located in the same directory (as the script being executed)?

    require File.expand_path(File.dirname(__FILE__) + &#39;/some_other_script&#39;)

I read that `require &quot;my_script&quot;` and `require &quot;./my_script&quot;` will actually load the script twice (ruby will not recognize that it is actually the same script), and this is the reason why `File.expand_path` is recommended: if it is used every time the script is required, then it will only be loaded once.

It seems weird to me that a concise language like Ruby does not seem to have a shorter solution.  For example, python simply has this:

    import .some_other_module_in_the_same_directory

I guess I could monkey-patch `require`... but that&#39;s just evil!  ;-)

Is there a shorter way to require a file in the same directory in ruby?

I have read several posts about issues that people are having with React Native and the `require()` function when trying to require a dynamic resource such as:

Dynamic **(fails)**:

    urlName = &quot;sampleData.json&quot;;
    data = require(&#39;../&#39; + urlName);

vs. Static **(succeeds)**:

    data = require(&#39;../sampleData.json&#39;);

I have read on some threads that this is a bug in React Native and in others that this is a feature.

Is there a new way to require a dynamic resource within a function?

Related Posts (all fairly old in React time):

 - https://stackoverflow.com/questions/33085341/importing-text-from-local-json-file-in-react-native
 - https://stackoverflow.com/questions/39901584/react-native-dynamically-list-require-files-in-directory
 - https://stackoverflow.com/questions/30854232/react-native-image-require-module-using-dynamic-names
 - https://stackoverflow.com/questions/43516269/react-native-how-to-use-requirepath-with-dynamic-urls

React Native: require() with Dynamic String?

I have Perl code which relies on `Term::ReadKey` to get the terminal width. My installation is missing this module, so I want to provide a default if the module isn&#39;t present rather than throw an exception.

How can I conditionally use an optional module, without knowing ahead of time whether it is available.

    # but only if the module is installed and exists
    use Term::ReadKey;
    ...

How can I accomplish this?

How can I require an optional Perl module if installed?

I&#39;m writing some code for Node.js and I&#39;m currently using JSHint to check over my code. However, when I use the `require` function to import modules, it says:
&gt; &#39;require&#39; is not defined.

How can I suppress the warning?

    &quot;use strict&quot;;
    var express = require(&#39;express&#39;);   
    var register = require(&#39;./routes/register&#39;);

Disabling warning about &quot;require&quot; function in JSHint

I need to check whether &quot;mocha&quot; is installed, before running it. I came up with the following code:

    try {
        var mocha = require(&quot;mocha&quot;);
    } catch(e) {
        console.error(e.message);
        console.error(&quot;Mocha is probably not found. Try running `npm install mocha`.&quot;);
        process.exit(e.code);
    }

I dont like the idea to catch an exception. Is there a better way?

Node.js - check if module is installed without actually requiring it

How do you check if an include / require_once exists before you call it, I tried putting it in an error block, but PHP didn&#39;t like that.

I think `file_exists()` would work with some effort, however that would require the whole file path, and a relative include could not be passed into it easily.

Are there any other ways?

Check if an include (or require) exists

I’m trying out webpack (http://webpack.github.io/) and it looks really nice, however I’m kind of stuck here.

Say that I’m using a CDN for a library, f.ex jQuery. Then in my code, I want the `require(&#39;jquery&#39;)` to automatically point to the global jquery instance, instead of trying to include it from my modules.

I’ve tried using plugins like the `IgnorePlugin`:

    new webpack.IgnorePlugin(new RegExp(&quot;^(jquery|react)$&quot;))

This works for ignoring the library, but it still says that the required module is &quot;missing&quot; when I run the webpacker.

Somehow I need to tell webpack that `jquery` should be picked up from the global context instead. Seems like a common use case, so I’m kind of surprised that the docs doesn’t target this specifically.

Webpack and external libraries

Is `require File.expand_path(..., __FILE__)` the best way to require other files within a project?

All Require Solutions on Gang of Coders

Total of 42 Require Solutions