javascript-obfuscator / javascript-obfuscator/webpack-obfuscator
How to onfuscate only my own code using webpack-obfuscator?
- Lingua principale
- TypeScript
- Stelle
- 928
- Fork
- 92
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
I'm building an electron application using TypeScript and WebPack. I want to process my own code without touching any 3rd party dependencies in order to rename only my own classes property names.
I've tried to use two approaches but with no success:
1) Using plugin
```typescript
import path from 'node:path';
import type { Configuration } from 'webpack';
import { rules } from './webpack.rules';
import WebpackObfuscator from 'webpack-obfuscator';
export const mainConfig: Configuration = {
/**
* This is the main entry point for your application, it's the first file
* that runs in the main process.
*/
entry: "./src/index.ts",
// Put your normal webpack config below here
module: {
rules
},
plugins: [
new WebpackObfuscator({
sourceMap: true,
renameProperties: true,
rotateStringArray: true
}, "node_modules/")
],
resolve: {
extensions: [".js", ".ts", ".jsx", ".tsx", ".css", ".json"],
// Workaround to make import aliases ("paths" from tscondig.json) work
// https://stackoverflow.com/a/75373097/6698055
alias: {
"@domain": path.resolve(__dirname, "src/domain"),
"@platform": path.resolve(__dirname, "src/platform"),
"@build_src": path.resolve(__dirname, "build_src")
}
}
};
```
2) Using loader
```typescript
import type { ModuleOptions } from 'webpack';
import WebpackObfuscator from 'webpack-obfuscator';
import path from 'node:path'
export const rules: Required["rules"] = [
// Add support for native node modules
{
// We're specifying native_modules in the test because the asset relocator loader generates a
// "fake" .node file which is really a cjs file.
test: /native_modules[/\\].+\.node$/,
use: "node-loader"
},
{
test: /[/\\]node_modules[/\\].+\.(m?js|node)$/,
parser: { amd: false },
use: {
loader: "@vercel/webpack-asset-relocator-loader",
options: {
outputAssetBase: "native_modules"
}
}
},
{
test: /\.js$/,
enforce: 'post', // Ensure this loader will be called after normal loaders
use: {
loader: WebpackObfuscator.loader,
options: {
rotateStringArray: true,
renameProperties: true
}
}
}
];
```
How can I force WebPack to process only my own code without touching any dependencies?
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia dalla configurazione principale di webpack e dalle regole in webpack.rules, concentrandoti sulle corrispondenze di plugin e loader per i moduli raggruppati. Esegui la build webpack di Electron e ispezionane l’output per determinare quali moduli sono offuscati. Il lavoro è completato quando il codice TypeScript dell’applicazione viene elaborato, mentre le dipendenze di terze parti rimangono invariate.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- electron, typescript, webpack
- Ambito
- build-system, desktop
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100