refactor: configure webpack not to follow symlinks (#286)

This change will make webpack not follow symlinks to their original location, and will enable us to work with symlinked packages during development.

Author: PanayotCankov

prepublish/common/exports.js

@@ -44,6 +44,10 @@ module.exports = env => {
             alias: {
                 '~': resolve("./app")
             },
+
+            // This will not follow symlinks to their original location,
+            // and will enable us to work with symlinked packages during development.
+            symlinks: false
         },
         node: {
             // Disable node shims that conflict with NativeScript

templates/webpack.angular.js

@@ -57,6 +57,10 @@ module.exports = env => {
             alias: {
                 '~': resolve("./app")
             },
+
+            // This will not follow symlinks to their original location,
+            // and will enable us to work with symlinked packages during development.
+            symlinks: false
         },
         node: {
             // Disable node shims that conflict with NativeScript

templates/webpack.javascript.js

@@ -54,6 +54,10 @@ module.exports = env => {
             alias: {
                 '~': resolve("./app")
             },
+
+            // This will not follow symlinks to their original location,
+            // and will enable us to work with symlinked packages during development.
+            symlinks: false
         },
         node: {
             // Disable node shims that conflict with NativeScript

templates/webpack.typescript.js

@@ -54,6 +54,10 @@ module.exports = env => {
             alias: {
                 '~': resolve("./app")
             },
+
+            // This will not follow symlinks to their original location,
+            // and will enable us to work with symlinked packages during development.
+            symlinks: false
         },
         node: {
             // Disable node shims that conflict with NativeScript