![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@newrelic/webpack-plugin
Advanced tools
An experimental plugin to allow New Relic's NodeJS Agent to work with webpack compiled server side javascript.
This project is an experimental plugin that allows New Relic's NodeJS Agent to work with webpack compiled server side javascript. This plugin does not automatically instrument any frontend javascript frameworks -- please see New Relic's browser agent documentation for more information on monitoring frontend javascript frameworks.
We distribute this plugin via NPM. To add it to your project, just run
$ npm install @newrelic/webpack-plugin
One installed, to get started add an externals
and plugins
section to your webpack configuration that looks something like this
/*...*/
const nodeExternals = require('@newrelic/webpack-plugin/lib/externals')
const NewrelicWebpackPlugin = require('@newrelic/webpack-plugin/lib/NewrelicWebpackPlugin')
module.exports = {
/* ... */
externals: [nodeExternals()],
plugins: [
new NewrelicWebpackPlugin()
]
/* ... */
}
In order to use Newrelic's NodeJS agent with webpack, you'll need to
require('newrelic')
to the top of your generated sources.This package allows you to do both. The nodeExternals
function
const nodeExternals = require('newrelic-webpack-plugin/lib/externals')
/* ... */
module.exports = {
/* ... */
externals: [nodeExternals()],
/* ... */
}
is borrowed from webpack-node-externals, which is the de-facto standard way to use webpack with NodeJS server side projects. If a module the agent instruments is not listed as a webpack external, the agent will not function properly.
The NewrelicWebpackPlugin
const NewrelicWebpackPlugin = require('newrelic-webpack-plugin/lib/NewrelicWebpackPlugin')
module.exports = {
/* ... */
plugins: [
new NewrelicWebpackPlugin()
]
/* ... */
}
ensures that a require('newrelic')
statment is added to the top of any .js
asset file generated by webpack.
You can run tests for this repository via npm
$ npm run test
New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices. Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub. You can find this project's topic/threads here:
https://discuss.newrelic.com/t/experimental-webpack-plugin-for-nodejs/88068/20
We encourage your contributions to improve the New Relic Webpack Plugin! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at opensource@newrelic.com.
New Relic Webpack Plugin is licensed under the Apache 2.0 License.
The New Relic Webpack Plugin also uses source code from third-party libraries. You can find full details on which libraries are used and the terms under which they are licensed in the third-party notices document.
Version 0.4.2
First public release.
Adds Github Repository to package.json
FAQs
An experimental plugin to allow New Relic's NodeJS Agent to work with webpack compiled server side javascript.
The npm package @newrelic/webpack-plugin receives a total of 0 weekly downloads. As such, @newrelic/webpack-plugin popularity was classified as not popular.
We found that @newrelic/webpack-plugin demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.