Atom-beautify: Object.extname is deprecated.

[fireice009]

Atom beta 1.13.0-beta8
atom-beautify 0.29.14

Remove and then install, the issue is still there.

Argument to path.extname must be a string

Object.extname (/Users/my/Downloads/Atom Beta.app/Contents/Resources/app.asar/src/electron-shims.js:20:10)
<unknown> (/Users/my/.atom/packages/atom-beautify/src/beautifiers/index.coffee:230:34)
Promise._execute (/Users/my/.atom/packages/atom-beautify/node_modules/bluebird/js/release/debuggability.js:299:9)
Promise._resolveFromExecutor (/Users/my/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:481:18)
new Promise (/Users/my/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:77:14)
<unknown> (/Users/my/.atom/packages/atom-beautify/src/beautifiers/index.coffee:226:18)

[Glavin001]

This is a result of https://github.com/atom/atom/commit/c876fd76f8daf7c3bd5932cdb488f17980197698 and https://github.com/atom/atom/pull/12300

[ftaiolivista]

Same for me. Atom 1.13.1 x64 on Linux

[kravlost]

Same here for Atom 1.14 and atom-beautify 0.29,17.

[tmdNinja]

same for Atom 1.13.1 and Atom-Beautify 0.29.17 on mac

[fedorovstas]

Same for me. Atom 1.13.1 Ubuntu 16.04.

[manueldziuba]

Also for me the same: Atom 1.13.1 ia32 on Windows 7 Pro, atom-beautify 0.29.17

[viralk]

Same for me: Atom 1.14.2, Windows 10 Pro, atom-beautify 0.29.17

[jaimemunera]

Same here: Atom v1.14.3 Mac OS (Sierra), atom-beautify 0.29.17

[kengggg]

Same here: Atom v1.14.3 macOS Sierra

[xtianF]

same-same el cap mac

[d4nirod]

Fixed updating to 1.14.4, no more deprecation warnings.

[shillem]

Same here: Atom 1.14.4 with macOS Sierra

[rishikrsharma]

same here Atom 1.14.4 with macOS Sierra
(Argument to path.extname must be a string)

[Olmer1st]

same for atom 1.15.0 Ubuntu 15.04

[FadhelC]

Same here Atom 1.15, Mac OS X (El Capitan)

[ShadowFM]

Same here.

Atom v. 1.16.0-beta0
Windows 10

[Arcanemagus]

@Glavin001 although the commits you reference are what is causing this to be shown to users, the actual problem is that filePath isn't being verified to have a value before it is used in a call to path.extname here (likely source of this), or here.

[Israaael]

Hi, I'm new. Not sure if this has been resolved or not. I'm having the same problem. W 10 pro x64, Atom 1.14.3 and beautify 0.29.17.

[dramaticsquirrel]

Atom 1.15.0 ia32
atom-beautify 0.29.17
Windows 10 Home

Seems to appear only when beautifying unsaved files.

[Glavin001]

Great eye @Arcanemagus! There is an open Pull Request being reviewed with should resolve this issue once it is merged: https://github.com/Glavin001/atom-beautify/pull/1573
Thank you all for your patience!

[Glavin001]

Published to v0.29.18