resolving module_path with __dirname

[NonPolynomial]

What does this PR cover?

Fixing the issue #64.

• required path - module in manager/utils.js
• resolving the module_path with __dirname

How can this be tested?

Initialize astrum pattern llibrary in arbitary folder (e.g. astrum init ./pttrns/)

Screenshots / Screencast

---

Reviewers

Review 1

• 👍

Review 2 (optional)

• 👍

By adding a +1 you are confirming you have...

• Witnessed the work behaving as expected (this could be on the author's machine or screencast).
• Checked for coding anti-patterns.

---

[RyanHavoc]

@NonPolynomial Thanks for this. I haven't had chance to test on a Mac yet but it looks good.

[NonPolynomial]

@RyanHavoc I have to thank you, I'm glad that I can contribute some to this awesome tool 👍

[mixn]

Any way that this could get merged, @RyanHavoc? :)

Also, thanks for this, @NonPolynomial. I think I would have picked it up otherwise, but you were faster. :)

[giothevanni]

Good question, I also pitched in in this fix and made a Pull Request in @NonPolynomial 's branch removing unnecessary dependencies ("global-modules") after resolving the path relatively, see https://github.com/NonPolynomial/astrum/pull/1

I'd also like to point out that this fix resolves issue #116 as well, enabling astrum users to install it locally, for example as a dev dependency, which is great for CI environments or usage with containers, not having to install the library globally in the image as well.

[giothevanni]

I tested the functionality in a Windows 7 VM and macOS Sierra successfully.

[NonPolynomial]

Hey guys,

i merged the commit from @giothevanni into my repo.

This should work now for Win 7, 8.1 and 10, and also on MacOS Sierra - thanks to @giothevanni for further fixes and testing.

FYI @RyanHavoc

[RyanHavoc]

@NonPolynomial @giothevanni Thanks for the work on this guys! Released it as 1.9.5.

[mixn]

Thank you all, this was way faster than I expected. :) Setting it up locally now. Cheers! 🍻

[NonPolynomial]

@RyanHavoc How is the progress on Release v2.0.0? Are those changes from @giothevanni and me conflicting with the current state of release/2.0.0 ?
Can we help to fix those conflicts?