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.
Stop generating two config files
See original GitHub issueI’d like to suggest that we remove the truffle-config.js file from our templates (Truffle boxes and the output of the truffle init command). It was only ever relevant on Windows, and we now have multiple documented workarounds such that it’s not necessary.
http://truffleframework.com/docs/advanced/configuration#resolving-naming-conflicts-on-windows
Also, it seems to confuse people, who don’t understand why it’s there.
I figure that if Truffle continues to accept the existence of a truffle-config.js in projects, but just doesn’t ship one with new projects, then we can implement this without any breaking changes.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (8 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
Why not just eliminate truffle.js and only recognize truffle-config.js? Works on all supported OSes.
@gnidan For sure, makes sense. I am much more in favor of retaining
truffle.jsanyway.