From 16e5ba0cba01eeec34a4362d8465fd16adddcfee Mon Sep 17 00:00:00 2001 From: sternenseemann Date: Tue, 21 Jul 2020 19:57:00 +0200 Subject: [PATCH] Add note that NODE_PATH is not supported browserify doesn't implicitly set opts.paths to NODE_PATH anymore unlike stated previously in this documentation. For background see: * https://github.com/browserify/resolve/issues/39#issuecomment-306223854 * https://github.com/browserify/resolve/pull/47 * https://github.com/browserify/browserify/issues/1626 --- readme.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.markdown b/readme.markdown index 527ece2..4a65c21 100644 --- a/readme.markdown +++ b/readme.markdown @@ -1293,7 +1293,7 @@ This is because your application is more tightly coupled to a runtime environment configuration so there are more moving parts and your application will only work when your environment is setup correctly. -node and browserify both support but discourage the use of `$NODE_PATH`. +browserify supports `opts.paths` (although discourages it), but does not support `$NODE_PATH`. ## non-javascript assets