fix(require): get rid of relative path to the word-wrap #5
Conversation
Fix this module for npm@3 where flat directory structure is "by default". A bit of background: If the module identifier passed to require() is not a native module, and does not begin with '/', '../', or './', then Node.js starts at the parent directory of the current module, and adds /node_modules, and attempts to load the module from that location. If it is not found there, then it moves to the parent directory, and so on, until the root of the file system is reached. This closes commitizen#4
fix(require): get rid of relative path to the word-wrap
|
Thanks, I'll cut a release with this shortly. |
|
Can you please republish it to npm as the latest? (I'm still getting the old relative word-wrap version) Thanks! |
|
@shairez Thanks. 1.1.1 has been released to npm. Can you try it again? |
|
Checked, still get an error I'm running on Windows, Get the following error: |
|
Thanks. I'll look into it.
|
|
@rodrigo-medeiros @shairez @Den-dp, I am having to roll back this PR for 1.1.2 and will be rewriting the cli and adapters for npm3 and node4. Since the core assumptions of where things are located have changed, it will probably introduce breaking changes and thus new npm and new node will be a 2.0.0 feature. I am already working on it but I wanted to make sure to give an update in this PR since it introduced some breaking changes for older node versions. |
|
Thanks @jimthedev for the update! |
Fix this module for npm@3 where flat directory structure is "by default". A bit of background: If the module identifier passed to require() is not a native module, and does not begin with '/', '../', or './', then Node.js starts at the parent directory of the current module, and adds /node_modules, and attempts to load the module from that location. If it is not found there, then it moves to the parent directory, and so on, until the root of the file system is reached.
This closes #4