remove puka

[nlf]

adding puka as a dependency here was an effort to make scripts defined in your package.json run in a more cross-platform compatible way, unfortunately the side effects seem to be largely undesirable.

as this is implemented today, things like expanding %Path% style environment variables is impossible, passing "" as a parameter gets lost entirely, and there are some inconsistencies in the way arguments are handled in different shells.

removing puka is a step toward being consistent instead of trying to make a script written for unix work in windows, which IMO is where our focus should lie (consistency).

References

Fixesnpm/cli#2731
Fixes#19

[nlf]

adding puka as a dependency here was an effort to make scripts defined in your package.json run in a more cross-platform compatible way, unfortunately the side effects seem to be largely undesirable.

as this is implemented today, things like expanding %Path% style environment variables is impossible, passing "" as a parameter gets lost entirely, and there are some inconsistencies in the way arguments are handled in different shells.

removing puka is a step toward being consistent instead of trying to make a script written for unix work in windows, which IMO is where our focus should lie (consistency).

References

Fixesnpm/cli#2731
Fixes#19

[nlf]

adding puka as a dependency here was an effort to make scripts defined in your package.json run in a more cross-platform compatible way, unfortunately the side effects seem to be largely undesirable.

as this is implemented today, things like expanding %Path% style environment variables is impossible, passing "" as a parameter gets lost entirely, and there are some inconsistencies in the way arguments are handled in different shells.

removing puka is a step toward being consistent instead of trying to make a script written for unix work in windows, which IMO is where our focus should lie (consistency).

References

Fixesnpm/cli#2731
Fixes#19

[nlf]

adding puka as a dependency here was an effort to make scripts defined in your package.json run in a more cross-platform compatible way, unfortunately the side effects seem to be largely undesirable.

as this is implemented today, things like expanding %Path% style environment variables is impossible, passing "" as a parameter gets lost entirely, and there are some inconsistencies in the way arguments are handled in different shells.

removing puka is a step toward being consistent instead of trying to make a script written for unix work in windows, which IMO is where our focus should lie (consistency).

References

Fixesnpm/cli#2731
Fixes#19

[nlf]

adding puka as a dependency here was an effort to make scripts defined in your package.json run in a more cross-platform compatible way, unfortunately the side effects seem to be largely undesirable.

as this is implemented today, things like expanding %Path% style environment variables is impossible, passing "" as a parameter gets lost entirely, and there are some inconsistencies in the way arguments are handled in different shells.

removing puka is a step toward being consistent instead of trying to make a script written for unix work in windows, which IMO is where our focus should lie (consistency).

References

Fixesnpm/cli#2731
Fixes#19

[nlf]

adding puka as a dependency here was an effort to make scripts defined in your package.json run in a more cross-platform compatible way, unfortunately the side effects seem to be largely undesirable.

as this is implemented today, things like expanding %Path% style environment variables is impossible, passing "" as a parameter gets lost entirely, and there are some inconsistencies in the way arguments are handled in different shells.

removing puka is a step toward being consistent instead of trying to make a script written for unix work in windows, which IMO is where our focus should lie (consistency).

References

Fixesnpm/cli#2731
Fixes#19

[nlf]

adding puka as a dependency here was an effort to make scripts defined in your package.json run in a more cross-platform compatible way, unfortunately the side effects seem to be largely undesirable.

as this is implemented today, things like expanding %Path% style environment variables is impossible, passing "" as a parameter gets lost entirely, and there are some inconsistencies in the way arguments are handled in different shells.

removing puka is a step toward being consistent instead of trying to make a script written for unix work in windows, which IMO is where our focus should lie (consistency).

References

Fixesnpm/cli#2731
Fixes#19

[nlf]

adding puka as a dependency here was an effort to make scripts defined in your package.json run in a more cross-platform compatible way, unfortunately the side effects seem to be largely undesirable.

as this is implemented today, things like expanding %Path% style environment variables is impossible, passing "" as a parameter gets lost entirely, and there are some inconsistencies in the way arguments are handled in different shells.

removing puka is a step toward being consistent instead of trying to make a script written for unix work in windows, which IMO is where our focus should lie (consistency).

References

Fixesnpm/cli#2731
Fixes#19