According to the Webpack documentation, you can use the externals property on the config object “to specify dependencies for your library that are not resolved by webpack, but become dependencies of the output. This means they are imported from the enviroment while runtime [sic].” The example on that page illustrates it really well, using jQuery. … Read more
There is a way of deducing the “local path” of a file (more concretely, the string that was used to load the file). If you are requiring a file inside lib.foo.bar, you might be doing something like this: require ‘lib.foo.bar’ Then you can get the path to the file as the first element (and only) … Read more
jshint is not aware of node.js globals by default you need to inform it. add this comment to the top: /* jshint node: true */
You should use require.resolve() instead of require(). require will load the library if found, but require.resolve() will not, it will return the file name of the module. See the documentation for require.resolve try { console.log(require.resolve(“mocha”)); } catch(e) { console.error(“Mocha is not found”); process.exit(e.code); } require.resolve() does throw error if module is not found so you … Read more
Since ruby 1.9 you can use require_relative. Check the latest doc for require_relative or another version of the Core API.
Here’s a bare-bones solution that does not require another module: my $rc = eval { require Term::ReadKey; Term::ReadKey->import(); 1; }; if($rc) { # Term::ReadKey loaded and imported successfully … } Note that all the answers below (I hope they’re below this one! 🙂 that use eval { use SomeModule } are wrong because use statements … Read more
Actually all you need to do is require ‘active_support/inflector’ and that will extend the String type. you can then do “MyString”.pluralize which will return “MyStrings” for 2.3.5 try: require ‘rubygems’ require ‘active_support/inflector’ should get it, if not try sudo gem install activesupport and then the requires.
As i have heard of, react’s require() only uses static url not variables, that means that you have to do require(‘/path/file’), take a look at this issue on github and this one for more alternative solutions, there are a couple of other ways to do it! for e.g const images = { profile: { profile: … Read more
It depends on your platform, and how Ruby was compiled, so there is no “the” answer to this. You can find out by running: ruby -e ‘puts $:’ Generally, though, you have the standard, site, and vendor Ruby library paths, including an arch, version, and general directory under each.
You can use this to delete its entry in the cache: delete require.cache[require.resolve(‘./b.js’)] require.resolve() will figure out the full path of ./b.js, which is used as a cache key.