
Research
/Security News
10 npm Typosquatted Packages Deploy Multi-Stage Credential Harvester
Socket researchers found 10 typosquatted npm packages that auto-run on install, show fake CAPTCHAs, fingerprint by IP, and deploy a credential stealer.
Small wrapper for Webpack, Babel and various Webpack loaders for Valu Digital Sakke projects.
Features
sakke.jsonassets/scriptsdist/scripts with a manifest.json filenpm install sakke
This tool uses https and you must point SAKKE_CA, SAKKE_CERT and SAKKE_KEY environment variables to localhost certificate.
Create sakke.config.js:
/** @type {import("sakke").Config} */
const config = {
// babelPlugins: [],
// webpackPlugins: [],
// webpackRules: [],
// compileNodeModules: [],
};
module.exports = config;
The type comment is just to help the editor autocomplete.
Run Wepback Dev Server, SASS watcher, live reload etc.
sakke dev
sakke build
To production
sakke deploy-production
Staging
sakke deploy-staging
JS specific tasks
Build for production
sakke js --production
Develop with the dev server
sakke js --serve
Analyze bundle contents
sakke js --analyze
Build CSS from SASS
sakke css
Run any legacy gulp task with
sakke gulp [task name]
If you need to customize the Webpack plugins you must import it from
sakke/webpack to ensure correct version is used.
Example
const webpack = require("sakke/webpack");
/** @type {import("sakke").Config} */
const config = {
webpackPlugins: [
new webpack.ContextReplacementPlugin(/moment[/\\]locale$/, /fi|en/),
],
};
module.exports = config;
This is needed when sakke build tool is used outside of WP theme context:
In sakke.json
{
"publicPath": "/wp-content/plugins/my-plugin/dist/scripts/"
}
@valu/webpack-configEnsure the project package "name" is not "sakke" in the package.json file.
Remove the wepback config package and other build packages
npm uninstall @valu/webpack-config @epeli/webpack-config cssnano gulp gulp-cssnano gulp-imagemin gulp-livereload gulp-postcss gulp-sass imagemin-pngcrush autoprefixer terser find-process
Install the new package and refresh the lock file
npm install sakke
rm -rf node_modules package-json.lock
npm install
Remove gulpfile(s)
rm -f gulpfile.js sakke-lib/gulpfile.js
Remove old jquery proxy
rm assets/scripts/lib/jquery.js
Other old crap too if present
rm -rf sakke-lib/tools sakke-lib/package*
Create sakke.config.js and copy babelPlugins, webpackPlugins and
compileNodeModules, webpackRules fields from webpack.config.js if
applicable.
Remove webpack.config.js
rm webpack.config.js
Fix scripts in package.json. Mostly just replace gulp with sakke since there is no gulp directly in the project anymore.
FAQs
Webpack and Babel wrapper for Sakke WordPress Themes
The npm package sakke receives a total of 307 weekly downloads. As such, sakke popularity was classified as not popular.
We found that sakke demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers 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.

Research
/Security News
Socket researchers found 10 typosquatted npm packages that auto-run on install, show fake CAPTCHAs, fingerprint by IP, and deploy a credential stealer.

Product
Socket Firewall Enterprise is now available with flexible deployment, configurable policies, and expanded language support.

Security News
Open source dashboard CNAPulse tracks CVE Numbering Authorities’ publishing activity, highlighting trends and transparency across the CVE ecosystem.