Support cache dependencies for cases where package lock files are located in subfolders
See original GitHub issueHi! 👋
We have a mixed-language monorepo with nothing in the base folder except some CI info. We need to be able to specify working-directory
input like other scripts in order to use this fantastic action to build our node subfolders.
Something like:
- uses: actions/setup-node@v2
with:
node-version: '14'
working-directory: some-client
Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:15
- Comments:6 (4 by maintainers)
Top Results From Across the Web
How to specifiy path for actions/setup-node in Github
Use cache-dependency-path for cases when multiple dependency files are used, or they are located in different subdirectories.
Read more >npm-install
GitHub Action for install npm dependencies with caching without any configuration. Latest version: 1.8.25, last published: 2 months ago.
Read more >Pipeline caching - Azure - Microsoft Learn
Pipeline caching can help reduce build time by allowing the outputs or downloaded dependencies from one run to be reused in later runs,...
Read more >Things I wish I had known when I started JavaScript monorepo ...
Only root level package-lock.json file is maintained. It contains information for installing the entire monorepo with all it's packages. None of ...
Read more >Caching (not only) NuGet packages on Azure DevOps
Locking dependencies. Before we configure cache task we need to lock dependencies to create packages.lock.json file as we need that file to set ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello everyone!
This feature request will be implemented soon. I have a small ADR under review https://github.com/actions/setup-node/pull/299 . Proposed approach is a bit different from proposed in this issue - we would like allow specifying full path (directory path + filename) to lock file instead of
working_directory
(directory path only). We believe this approach will be a bit more generic and unblock more use-cases.Hello everyone, pull request with adding support of specifying lock files was merged. I’m closing the issue if you have any concerns, feel free to reopen it or ping me in the thread.