You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually, it might be better to just document that the user should provide an absolute path to Typo, which they can get using the path.join. I think that's more robust in the long run
I am trying to use the library and I 'm still getting Error: ENOENT, no such file or directory for the dictionaries path. Giving the absolute path still doesn't work for me. I also saw in your code that fs.existsSync(path) (line 167) is deprecated and I changed it to fs.statSync(path) but it did not work either.
@Stoup I think it would be best for you to open up a stackoverflow question and post some more details about your code, otherwise it's difficult to help
I found that if I try to give
Typo
a relative path to my dictionaries in node, it throws an error likeI think that's happening because of this check, which will be relative to
node_module/typo-js/typo.js
I think it can be fixed by something like, which works for me locally.
I can make a PR to update this
The text was updated successfully, but these errors were encountered: