Make package.json optional
See original GitHub issueHello,
This action looks great!
However, I cannot help but notice that it wants a package.json
. I saw we can choose where it is located.
But can we use this action when we don’t have a package.json
at all? Like for any project which is not based on npm
(could be maven, gradle, cargo, elm, you name it)
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
package.json - npm Docs
Marking a peer dependency as optional ensures npm will not emit a warning if the soy-milk package is not installed on the host....
Read more >What Are NPM's Optional Dependencies and When Should ...
Finally, optionalDependencies are dependencies that don't necessarily need to be installed. If a dependency can be used, but you would like npm ......
Read more >What are Optional Dependencies and when should we use them
The term optional dependencies apply to dependencies that won't cause a failure during the installation of an application or project since ...
Read more >node.js - Optional dependencies in npm?
declare optional dependencies in package.json that aren't automatically installed by npm install , say optionalPeerDependencies; a custom require -style ...
Read more >node.js - package-lock.json file, package with "optional": true
After a package is removed from dependencies, its dependencies are marked "optional": true in package ...
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 Free
Top 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
This is released in v3
@jcornaz the json file is used to know what the latest version was and what the next version will be, so doing
echo "{ \"version\": \"0.0.0\" }" > package.json
will result in creating the same version again and again.To solve that we can add logic to do it based on the latest tag.
I added this to the V3 milestone, tasks for this issue is:
package-json
toversion-file
version-path
so users can define which value to updateskip-file
to not update any file and use GIT tags for versioningskip-tag
to not create a tag and use file for versioning