New:Microsoft Teams Notifications Are Now Available in Socket.Learn more
Get Started

@syncrona/webpack-plugin

Package Overview
Dependencies
Maintainers
1
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@syncrona/webpack-plugin

SyncroNow AI build plugin that bundles files with Webpack in the ServiceNow sync pipeline (honors webpack.config.js and sync.config.js).

latest
Source
npmnpm
Version
1.0.0
Version published
Weekly downloads
2
-90.91%
Maintainers
1
Weekly downloads
 
Created
Source

@syncrona/webpack-plugin

npmnodelicenseCITypeScript

Overview

SyncroNow AI is the ServiceNow scoped-application toolchain behind the syncrona CLI. This package is one of its build plugins: register it in the rules array of your sync.config.js and syncrona build runs it over every matching file.

This plugin allows you to run Webpack on your desired files. This allows you to build frontend bundles in a more modern way or even potentially bundle server side javascript files.

Installation

npm i -D @syncrona/webpack-plugin

Options

KeyTypeDefaultDescription
configGenerator(context:Sync.FileContext)=>webpack.Configuration()=>{}Function that can generate a webpack configuration object. A Sync.FileContext is passed in so that you can substitute options using the context
webpackConfigwebpack.Configuration{}Same as webpack.config.js object

Order of Configurations

  • Load from closest webpack.config.js.
  • Load from webpackConfig in sync.config.js and override any overlapping values.
  • Run configGenerator() from configGenerator option in sync.config.js and override any overlapping values.

Example Usage

This example takes .wp.js files and bundles them with webpack by generating the options with a function

//sync.config.js
module.exports={
  rules:{
    match:/\.wp\.js$/,
    plugins:[
      name:"@syncrona/webpack-plugin",
      options:{
        configGenerator:(context)=>{
          mode:"production",
          //set name of record as the library name
          library:context.name
        }
      }
    ]
  }
};

FAQs

Package last updated on 25 Aug 2026

Related posts