fix(init): fix init prompt installation

[rishabh3112]

What kind of change does this PR introduce?

bugfix
Did you add tests for your changes?
N/A
If relevant, did you update the documentation?
N/A
Summary
#741

Does this PR introduce a breaking change?

No
Other information

[evenstensberg]

You can see how we did this at the next branch

[rishabh3112]

Hi @evenstensberg, next branch has refactored bin into lib, can you point me where to find installation prompt ?

[evenstensberg]

You can navigate the lib folder, it's not that big, and you learn the new internals

[rishabh3112]

@evenstensberg we don't do a global installation of @webpack-cli/init as per next branch instead forcing users to do a local installation. So next branch code doesn't encounter the error this PR supposed to solve. So there are two solutions:

1. revert global installation setup to local for @webpack-cli/init as in next branch ( I don't like this personally)
2. Get location to the global @webpack-cli/init package by getting prefix programatically using npm.

Which one I should implement?

[evenstensberg]

Do as 1. Does it and ill review

[webpack-bot]

@rishabh3112 Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@evenstensberg Please review the new changes.

[rishabh3112]

Did that @evenstensberg

[rishabh3112]

Any review here 😅?
@evenstensberg

[rishabh3112]

Done @evenstensberg

[ghost]

There were the following issues with this Pull Request

• Commit: f9c130d
  • ✖ message may not be empty
  • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[ghost]

There were the following issues with this Pull Request

• Commit: f9c130d
  • ✖ message may not be empty
  • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[rishabh3112]

@evenstensberg after rebase with master NodeJS stable is failing on this PR.

failing on master too.
I have fixed commit messages here and this PR ready for review.

[rishabh3112]

@evenstensberg After investigation error is certainly due to jest-util package having the error as per Node v11.11.0 (stable). it's working fine at lower node versions.

pasting error for the reference.

TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#<process>'
      at exports.default (node_modules/jest-util/build/create_process_object.js:15:34)

[evenstensberg]

Any fix to this?

[rishabh3112]

@evenstensberg This is fixed at jest.

[rishabh3112]

Updating jest to v24.3.0 would fix this.

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.