-
Notifications
You must be signed in to change notification settings - Fork 16
Conversation
the issue #65 is produced to the wrong path to the htmlhint file. My previous fix attempt by changing to exec instead of execNode was just a workaround. I didn't notice the wrong path.
The |
What version of Atom are you using? |
Just looked over the rest of the comments in #65, and then checked on the So although this is the "wrong" path for executing the Something like: "HTMLHint Node executable" is probably enough to hint as to which one that should be chosen. |
I am using Windows 10 and Atom 1.4. NodeJS was installed while installing the plugin. Afterwards I uninstalled NodeJS to test the issue without NodeJS installed. |
// This is the wrapper script ("system binary") which requires node to be installed
path.join(__dirname, '..', 'node_modules', '.bin', 'htmlhint');
// This is the node executable script, which Atom can run and the above are wrappers around
path.join(__dirname, '..', 'node_modules', 'htmlhint', 'bin', 'htmlhint');
// This is the (minified) htmlhint script itself, and is not executable unless ran through something
path.join(__dirname, '..', 'node_modules', 'htmlhint', 'lib', 'htmlhint.js'); |
thanks for clarification. I changed the name of the setting to 'HTMLHint Node Script Path' |
Push it up, and assuming @johnwebbcole has no comments we can get it merged 😉. |
Ready. I forgot to push |
It's ok with me... The original script used the bin, not the .bin. I like the .bin idea, but it doesn't look like it's valid on all platforms |
Looks like Atom didn't get added to the PATH in the AppVeyor build for some reason, pinged @steelbrain to rebuild that then we can merge. |
the issue #65 is produced to the wrong path to the htmlhint file. My previous fix attempt by changing to exec instead of execNode was just a workaround. I didn't notice the wrong path.