René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"javascript-obfuscator break Assignment without declaration.","articleBody":"javascript-obfuscator break Assignment without declaration.\r\n\r\nThis issue is edited after post.\r\n\r\n~~~js\r\nfunction main() {\r\n  const o = {v: 1}\r\n  let v;\r\n  ({v} = o);\r\n  console.log(v);\r\n}\r\n\r\nmain();\r\n~~~\r\n\r\n## Expected Behavior\r\n\r\nstdout `1`.\r\n\r\n## Current Behavior\r\n\r\nstdout `undefined`.\r\n\r\n## Steps to Reproduce (for bugs)\r\n\r\n`yarn javascript-obfuscator src/main.js`\r\n\r\n## Your Environment\r\n\r\n* Obfuscator version used: 0.18.1\r\n* Node version used: v9.11.2\r\n\r\n# Stack trace\r\n\r\nNone.\r\n\r\n## Minimal working example that will help to reproduce issue\r\n\r\n`src/main.js`\r\n\r\n~~~js\r\nfunction main() {\r\n  const o = {v: 1}\r\n  let v;\r\n  ({v} = o);\r\n  console.log(v);\r\n}\r\n\r\nmain();\r\n~~~\r\n\r\ncommand.\r\n\r\n~~~sh\r\nyarn javascript-obfuscator src/main.js\r\n~~~\r\n\r\ncompiled.\r\n\r\n~~~js\r\nfunction main() {\r\n  const _0x501e82 = { v: 0x1 };\r\n  let _0x5b6c40;\r\n  ({ v } = _0x501e82);\r\n  console[\"log\"](_0x5b6c40);\r\n}\r\nmain();\r\n~~~\r\n\r\n# detail\r\n\r\nI use javascript-obfuscator.\r\nMy software is breaked.\r\nI found small example.\r\n\r\n~~~js\r\nfunction main() {\r\n  const o = {v: 1}\r\n  let v;\r\n  ({v} = o);\r\n  console.log(v);\r\n}\r\n\r\nmain();\r\n~~~\r\n\r\nThe code at 3 of lines is standard JavaScript statement.\r\n\r\n\u003e The round braces ( ... ) around the assignment statement is required syntax when using object literal destructuring assignment without a declaration.\r\n\u003e\r\n\u003e {a, b} = {a: 1, b: 2} is not valid stand-alone syntax, as the {a, b} on the left-hand side is considered a block and not an object literal.\r\n\u003e\r\n\u003e However, ({a, b} = {a: 1, b: 2}) is valid, as is var {a, b} = {a: 1, b: 2}\r\n\u003e\r\n\u003e NOTE: Your ( ... ) expression needs to be preceded by a semicolon or it may be used to execute a function on the previous line.\r\n\u003e\r\n\u003e [Destructuring assignment - JavaScript | MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment#Assignment_without_declaration)\r\n\r\n## webpack-obfuscator or obfuscator-loader\r\n\r\nI use `webpack.config.js`.\r\n\r\n~~~js\r\nconst JavaScriptObfuscator = require(\"webpack-obfuscator\");\r\nconst path = require(\"path\");\r\n\r\nmodule.exports = {\r\n  entry: {\r\n    main: \"./src/main.js\"\r\n  },\r\n  output: {\r\n    path: path.resolve(__dirname, \"app\"),\r\n    filename: \"[name].js\"\r\n  },\r\n  plugins: [new JavaScriptObfuscator()]\r\n};\r\n~~~\r\n\r\n* `yarn webpack --mode development \u0026\u0026 node app/main.js` output `1` (expected).\r\n* `yarn webpack --mode production \u0026\u0026 node app/main.js` output `undefined` (error).\r\n\r\nwebpack-obfuscator in production compile code as below.\r\n\r\n~~~js\r\n  function(e, n) {\r\n    ({ v: v } = { v: 1 }), console[_0xef72(\"0xb\")](void 0);\r\n  }\r\n~~~\r\n\r\nThis code ends of files.\r\n\r\nI wondered whether to post to the issue of webpack-obfuscator,\r\nSince I confirmed that the same problem will also occur in obfuscator-loader,\r\nI decided to post a problem on javascript-obfuscator issue.\r\n","author":{"url":"https://github.com/ncaq","@type":"Person","name":"ncaq"},"datePublished":"2018-09-06T09:22:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/328/javascript-obfuscator/issues/328"}