Update examples to use new package.json scripts
See original GitHub issueFeature Request
Update examples to use recently updated package.json
scripts from typescript starter.
Is your feature request related to a problem? Please describe.
Describe the solution you’d like
Teachability, Documentation, Adoption, Migration Strategy
What is the motivation / use case for changing the behavior?
Users should be able to use examples with latest installed version of nest.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
scripts - npm Docs
The "scripts" property of your package.json file supports a number of built-in scripts and their preset life cycle events as well as arbitrary...
Read more >An Introduction to Package JSON Scripts in Node.js
Lots of Node.js codebases use the package.json file as an essential component. Here is an introduction to effectively using `package.json` ...
Read more >How to update each dependency in package.json to the latest ...
to update just one dependency just use the following command: npm install yourPackage@latest. For example: My package.json file has dependency:
Read more >Scripting inside package.json
Typically we can have a scripts section, where we define json like key value script , Where Key is the command name which...
Read more >package.json Quick Start Guide | phoenixNAP KB
To manage your package.json file, use the npm command line interface, which comes bundled with Node.js. The npm tool comes with many commands ......
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
@rubin I think the problem with adding in the code I helped you with, the
tsconfig-path-bootstrap
is that it needs to be configurable for non-standard tsconfig names or for different use cases like monorepos. The added file helps, but honestly I think the deeper issues is withtsconfig-paths
which I haven’t dug deeper into. The other thing is that not everyone uses path mapping, so now a new file shows up and some users could be confused by it. Rather, this may need to be brought up to the author oftsconfig-paths
as that whether the real issue lies. The bootstrap script is a workaround, not a perfect solutionThis thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.