Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Separate build config from package.json
See original GitHub issue- Version: latest
- Target: mac, win, linux
I think it might be nice thing to consider to separate the build from package.json to a separate file, e.g. build.json. It could be optional in a way that either build key in package.json or build.json would apply if present, similar to what ava has. What do you think?
It could make large package.jsons more readable. If we already have 250 lines in package.json another 50-100 lines for build config make it quite unreadable.
I did a quick search in issues and couldn’t find anything related, so sorry if this has already been discussed here.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I am going to add support for
jsonandjson5to be sure that users are happy 😃Hi @develar, are there any plans to add
--configparameter so the config YAML can have different locations?