| copyright |
|
||
|---|---|---|---|
| lastupdated | 2017-07-18 |
{:shortdesc: .shortdesc} {:new_window: target="_blank"} {:codeblock: .codeblock}
{: #configuration_options} {: shortdesc}
A variety of options are available for configuring the sdk-for-nodejs buildpack.
{: #npm_scripts}
NPM provides a scripting facility allowing you to run scripts, including preinstall and postinstall scripts which are applied before and after your node_modules are installed. See npm-scripts 
for complete details.
{: #cache_behavior} {{site.data.keyword.Bluemix}} maintains a cache directory per node application, that is persisted between builds. The cache stores resolved dependencies so they are not downloaded and installed every time the app is deployed. For example, suppose myapp depends on express. Then the first time myapp is deployed the express module is downloaded. On subsequent deployments of myapp, the cached instance of express is used. The default behavior is to cache all node_modules installed by NPM and bower_components installed by bower.
Use the NODE_MODULES_CACHE variable to determine whether or not the Node buildpack uses or ignores the cache from previous builds. The default value is true. To disable caching set NODE_MODULES_CACHE to false, for example via the cf command line:
$ cf set-env myapp NODE_MODULES_CACHE false
{: codeblock}
Note that node_modules that are included in your application are not cached.
You can use a cacheDirectories array in your top-level package.json to achieve fine grained control over what modules are cached. When the cacheDirectories element is present in the package.json only those modules which are in the cacheDirectories array will be cached. In the following example only node_modules and bower_components are cached.
{
"cacheDirectories": ["node_modules","bower_components"],
...
}
{: codeblock}