<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?) in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726999#M5563</link>
    <description>&lt;P&gt;&lt;SPAN&gt;I attempted to use the AppD NodeJS agent to monitor a single-page application (SPA) built on NodeJS using React - webpack . However, since these SPAs only use NodeJS as a building block and the communication between the frontend and backend is direct (not via the frontend server), the AppD BRUM monitoring is more suitable than the NodeJS agent for monitoring the necessary metrics.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 15 May 2023 08:59:56 GMT</pubDate>
    <dc:creator>Sahil_Gupta2</dc:creator>
    <dc:date>2023-05-15T08:59:56Z</dc:date>
    <item>
      <title>Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726989#M5553</link>
      <description>&lt;P&gt;When trying to install the AppDynamics package for monitoring a Node.js application, our Webpack build process is not able to import a handful of dependencies. Specifically, the errors output are:&lt;/P&gt;
&lt;PRE&gt;WARNING in ./node_modules/appdynamics/lib/core/agent.js 445:8-28
require.main.require is not supported by webpack.
@ ./node_modules/appdynamics/index.js 1:17-44
@ ./server.ts

ERROR in ./node_modules/appdynamics-zmq/lib/index.js
Module not found: Error: Can't resolve '../zmq' in '.../my-app/node_modules/appdynamics-zmq/lib'
@ ./node_modules/appdynamics-zmq/lib/index.js 24:10-27
@ ./node_modules/appdynamics-zmq/index.js
@ ./node_modules/appdynamics/lib/libproxy/proxy-transport.js
@ ./node_modules/appdynamics/lib/libproxy/libproxy.js
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts

ERROR in ./node_modules/appdynamics-libagent/index.js
Module not found: Error: Can't resolve './appd_libagent' in '.../my-app/node_modules/appdynamics-libagent'
@ ./node_modules/appdynamics-libagent/index.js 36:9-35
@ ./node_modules/appdynamics/lib/libagent/libagent-connector.js
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts

ERROR in ./node_modules/appdynamics-native/index.js
Module not found: Error: Can't resolve './appdynamics' in '.../my-app/node_modules/appdynamics-native'
@ ./node_modules/appdynamics-native/index.js 29:10-34
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts

ERROR in ./node_modules/appdynamics-protobuf/index.js
Module not found: Error: Can't resolve './protobuf_for_node' in '.../my-app/node_modules/appdynamics-protobuf'
@ ./node_modules/appdynamics-protobuf/index.js 29:10-40
@ ./node_modules/appdynamics/lib/libproxy/proxy-transport.js
@ ./node_modules/appdynamics/lib/libproxy/libproxy.js
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts

ERROR in ./node_modules/log4js/lib/appenders/hipchat.js
Module not found: Error: Can't resolve 'hipchat-notifier' in '.../my-app/node_modules/log4js/lib/appenders'
@ ./node_modules/log4js/lib/appenders/hipchat.js 3:14-41
@ ./node_modules/log4js/lib/appenders sync ^\.\/.*$
@ ./node_modules/log4js/lib/log4js.js
@ ./node_modules/appdynamics/lib/core/logger.js
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts

ERROR in ./node_modules/log4js/lib/appenders/loggly.js
Module not found: Error: Can't resolve 'loggly' in '.../node_modules/log4js/lib/appenders'
@ ./node_modules/log4js/lib/appenders/loggly.js 3:11-28
@ ./node_modules/log4js/lib/appenders sync ^\.\/.*$
@ ./node_modules/log4js/lib/log4js.js
@ ./node_modules/appdynamics/lib/core/logger.js
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts

ERROR in ./node_modules/log4js/lib/appenders/mailgun.js
Module not found: Error: Can't resolve 'mailgun-js' in '.../my-app/node_modules/log4js/lib/appenders'
@ ./node_modules/log4js/lib/appenders/mailgun.js 34:14-35
@ ./node_modules/log4js/lib/appenders sync ^\.\/.*$
@ ./node_modules/log4js/lib/log4js.js
@ ./node_modules/appdynamics/lib/core/logger.js
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts

ERROR in ./node_modules/log4js/lib/appenders/smtp.js
Module not found: Error: Can't resolve 'nodemailer' in '.../my-app/node_modules/log4js/lib/appenders'
@ ./node_modules/log4js/lib/appenders/smtp.js 4:13-34
@ ./node_modules/log4js/lib/appenders sync ^\.\/.*$
@ ./node_modules/log4js/lib/log4js.js
@ ./node_modules/appdynamics/lib/core/logger.js
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts

ERROR in ./node_modules/log4js/lib/appenders/slack.js
Module not found: Error: Can't resolve 'slack-node' in '.../node_modules/log4js/lib/appenders'
@ ./node_modules/log4js/lib/appenders/slack.js 2:12-33
@ ./node_modules/log4js/lib/appenders sync ^\.\/.*$
@ ./node_modules/log4js/lib/log4js.js
@ ./node_modules/appdynamics/lib/core/logger.js
@ ./node_modules/appdynamics/lib/core/agent.js
@ ./node_modules/appdynamics/index.js
@ ./server.ts&lt;/PRE&gt;

&lt;P&gt;Our project is set up with:&lt;BR /&gt;- Webpack v4.29.0&lt;BR /&gt;- Node.js v11.0.0&lt;BR /&gt;- Appdynamics v4.5&lt;/P&gt;
&lt;P&gt;The Appdynamics usage is at the top of our server file as:&lt;/P&gt;
&lt;PRE&gt;// AppDynamics monitoring
require("appdynamics").profile({
controllerHostName: ***
controllerPort: 443,
controllerSslEnabled: true,
accountName: ****
accountAccessKey: ***
applicationName: ***
tierName: ***
nodeName: '01'
});&lt;/PRE&gt;

&lt;P&gt;And our Webpack configuration is:&lt;/P&gt;
&lt;PRE&gt;const path = require('path');
const webpack = require('webpack');

module.exports = {
entry: { server: './server.ts' },
resolve: { extensions: ['.js', '.ts'] },
target: 'node',
mode: 'development',
// this makes sure we include node_modules and other 3rd party libraries
externals: [/node_modules/],
output: {
path: path.join(__dirname, 'dist'),
filename: '[name].js'
},
module: {
rules: [{ test: /\.ts$/, loader: 'ts-loader' }]
},
plugins: [
]
};&lt;/PRE&gt;

&lt;P&gt;So far we have tried downgrading the Webpack version, downgrading the Node environment to 10.15, and using other import methods for the AppDynamics package, but this seems like an issue internal to the Appdynamics library?&lt;BR /&gt;&lt;BR /&gt;Has anyone experienced anything similar? Or had success using the Appdynamics node package with Webpack?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 15:58:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726989#M5553</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2019-03-08T15:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726990#M5554</link>
      <description>&lt;P&gt;Hi Cody,&lt;/P&gt;

&lt;P&gt;Could you try adding "appdynamics" to the externals array? Let me know if that helps.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:36:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726990#M5554</guid>
      <dc:creator>Kyle_Furlong</dc:creator>
      <dc:date>2019-03-11T22:36:48Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726991#M5555</link>
      <description>&lt;P&gt;Thank you Kyle, that did the trick!&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 20:05:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726991#M5555</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2019-03-13T20:05:15Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726992#M5556</link>
      <description>&lt;P&gt;The other fix I see is as below:&lt;/P&gt;
&lt;P&gt;ensure you're installing the 4.5.11 or higher version of the agent (@latest will work)&lt;/P&gt;
&lt;OL start="2"&gt;
&lt;LI&gt;install with npm install&lt;/LI&gt;
&lt;LI&gt;edit the package-lock.json file to remove the lines and sections that show jre / proxy&lt;/LI&gt;
&lt;LI&gt;"appdynamics-jre": "&lt;A href="https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-jre.tgz" target="_blank" rel="nofollow noopener noreferrer"&gt;https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-jre.tgz&lt;/A&gt;",&lt;/LI&gt;
&lt;LI&gt;"appdynamics-proxy": "&lt;A href="https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-proxy.tgz" target="_blank" rel="nofollow noopener noreferrer"&gt;https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-proxy.tgz&lt;/A&gt;",&lt;/LI&gt;
&lt;LI&gt;"appdynamics-jre": { "version": "&lt;A href="https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-jre.tgz" target="_blank" rel="nofollow noopener noreferrer"&gt;https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-jre.tgz&lt;/A&gt;", "integrity": "sha512-hmnixIubwz8TBxQMe1/5QYwxmrCsnimYrZvNbvWZHOx2XifRnenzaPHw3avFCTvXgkTWt5lsY3UBIqlDYxTg3Q==" },&lt;/LI&gt;
&lt;LI&gt;"appdynamics-proxy": { "version": "&lt;A href="https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-proxy.tgz" target="_blank" rel="nofollow noopener noreferrer"&gt;https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-proxy.tgz&lt;/A&gt;", "integrity": "sha512-1E+UxBrR4Vo0FAG0z+66RYx3dGZfb55W+6G/lTnDxt3U0TZUzA/rKo9PaQNDLKwogcgkraZYgBFYlVsvtvQy4w==" },&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Thu, 28 Mar 2019 12:00:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726992#M5556</guid>
      <dc:creator>Umervali_Niyama</dc:creator>
      <dc:date>2019-03-28T12:00:21Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726993#M5557</link>
      <description>I’ve also had to do similar within our yarn.lock file, specifically when encountering:&lt;BR /&gt;info Visit &lt;A href="https://yarnpkg.com/en/docs/cli/install" target="_blank" rel="nofollow noopener noreferrer"&gt;https://yarnpkg.com/en/docs/cli/install&lt;/A&gt; for documentation about this command.&lt;BR /&gt;error &lt;A href="https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-proxy.tgz" target="_blank" rel="nofollow noopener noreferrer"&gt;https://packages.appdynamics.com/nodejs/4.5.11.0/appdynamics-proxy.tgz&lt;/A&gt;: Integrity check failed for "appdynamics-proxy" (computed integrity doesn't match our records, got "sha1-wcdDKNB8QnI4D/YdYd+hAc6Ywy4=")&lt;BR /&gt;&lt;BR /&gt;It seems like there is something about the node.js AppDynamics library which, at minimum, isn’t configured in a typical way. Maybe it’s just related to how they host their own children dependencies?&lt;BR /&gt;</description>
      <pubDate>Fri, 12 Apr 2019 16:24:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726993#M5557</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2019-04-12T16:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726994#M5558</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;I am also facing a similar problem, all i am doing is adding the dependency as below in my package.json and it fails with the error shown below.&lt;/P&gt;

&lt;PRE&gt;"axios": "^0.18.0",
"appdynamics": "^4.3.7",
"d3-axis": "^1.0.12",
"d3-geo": "^1.11.3",
&lt;/PRE&gt;
&lt;P&gt;Error:&lt;/P&gt;
&lt;PRE&gt;./node_modules/appdynamics-zmq/lib/index.js
Module not found: Can't resolve '../zmq' in 'Drive:\myapp\mymodule\node_modules\appdynamics-zmq\lib'&lt;/PRE&gt;
&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2019 20:18:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726994#M5558</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2019-06-07T20:18:37Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726995#M5559</link>
      <description>&lt;P&gt;can you tell m e external arrays means&amp;nbsp; plz ?&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;@Anonymous&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;Thank you Kyle, that did the trick!&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Tue, 18 Jun 2019 14:11:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726995#M5559</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2019-06-18T14:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726996#M5560</link>
      <description>&lt;P&gt;4.5.16 agent has the fix for this . Tested&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2019 13:57:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726996#M5560</guid>
      <dc:creator>Umervali_Niyama</dc:creator>
      <dc:date>2019-06-24T13:57:56Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726997#M5561</link>
      <description>&lt;P&gt;I updated my externals array in webpack.base.babel.js as shown:&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2020-01-10 at 3.09.17 PM.png" style="width: 662px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/35080i4F9CF8762A4DAAAB/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;That made webpack happy, but when I try to run the app it crashes and I see this in my console:&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2020-01-10 at 3.11.07 PM.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/35082iEADF1E09DAAE2972/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I'm trying to evaluate AppDynamics, but I can't even install it properly. Please tell me what to do to fix this!&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2020 23:12:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726997#M5561</guid>
      <dc:creator>J_R__Willett</dc:creator>
      <dc:date>2020-01-10T23:12:41Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726998#M5562</link>
      <description>&lt;P&gt;Hi J.R.,&lt;/P&gt;&lt;P&gt;I believe externals is an array of module names, but more importantly you can skip it altogether with the following: &lt;A href="https://stackoverflow.com/a/41063795" target="_blank" rel="nofollow noopener noreferrer"&gt;https://stackoverflow.com/a/41063795&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Let us know if that helps!&lt;/P&gt;</description>
      <pubDate>Sat, 11 Jan 2020 00:22:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726998#M5562</guid>
      <dc:creator>Kyle_Furlong</dc:creator>
      <dc:date>2020-01-11T00:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to bundle Node.js with Appdynamics using Webpack (broken dependencies?)</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726999#M5563</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I attempted to use the AppD NodeJS agent to monitor a single-page application (SPA) built on NodeJS using React - webpack . However, since these SPAs only use NodeJS as a building block and the communication between the frontend and backend is direct (not via the frontend server), the AppD BRUM monitoring is more suitable than the NodeJS agent for monitoring the necessary metrics.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2023 08:59:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Unable-to-bundle-Node-js-with-Appdynamics-using-Webpack-broken/m-p/726999#M5563</guid>
      <dc:creator>Sahil_Gupta2</dc:creator>
      <dc:date>2023-05-15T08:59:56Z</dc:date>
    </item>
  </channel>
</rss>

