conventional-changelog/standard-version

Invalid path in lifecycle script

Open

#433 opened on Aug 13, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (7,442 stars) (825 forks)batch import
help wantedquestion

Description

I'm trying to replace the version number in one of my project's file at the postbump lifecycle script:

"scripts": {
  "postbump": "sed -i -r 's/(<span id=\"app-version\">)[^<]*(<\\/span>)/\\1$npm_package_version\\2/' app/views/footer.scala.html && git add app/views/footer.scala.html"
}

I tested the command beforehand and it works, but when I run it in the lifecycle, I get

The specified path is invalid. Error

I know the specified path is actually valid, so the problem must be elsewhere.

Contributor guide

Tech stack
javascriptnodejsshell
Domain
toolingrelease
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
npm scriptssed commandpath handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The error 'The specified path is invalid' likely originates from npm or the OS when executing the lifecycle script. Investigate how standard version executes postbump scripts and whether the path resolution differs from direct command execution. Check if the issue is specific to Windows paths or relative paths. Look at the repository's issue #433 and any similar closed issues. Consider testing the same sed command in different environments to confirm the root cause.