javascript-obfuscator / javascript-obfuscator/webpack-obfuscator

How to onfuscate only my own code using webpack-obfuscator?

Ouverte
#178 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
TypeScript
Étoiles
928
Forks
92
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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?

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Commencez par la configuration principale de webpack et les règles de webpack.rules, en vous concentrant sur les correspondances des plugins et des loaders pour les modules regroupés. Exécutez le build webpack d’Electron et inspectez sa sortie afin de déterminer quels modules sont obfusqués. Le travail est terminé lorsque le code TypeScript de l’application est traité, tandis que les dépendances tierces restent inchangées.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
electron, typescript, webpack
Domaine
build-system, desktop
Type d'issue
Bug
Difficulté
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.