Stuck on an issue?
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.
Add editorConfig properties to package.json?
See original GitHub issueIn the spirit of ESLint and Babel, would it make sense to allow editorConfig settings in package.json? I feel like it probably doesn’t, but I wanted to have it documented either way to be definitive.
i.e.
"editorConfig" : {
}
Could also add presets: https://github.com/editorconfig/editorconfig-core-js/issues/31
Issue Analytics
- State:
- Created 8 years ago
- Reactions:27
- Comments:39 (11 by maintainers)
Top Results From Across the Web
EditorConfig
EditorConfig is a file format and collection of text editor plugins for maintaining consistent coding styles between different editors and IDEs.
Read more >EditorConfig settings - Visual Studio (Windows) - Microsoft Learn
Open a project or solution in Visual Studio. · From the menu bar, choose Project > Add New Item, or press Ctrl+Shift+A. ·...
Read more >EditorConfig | IntelliJ IDEA Documentation - JetBrains
Add an .editorconfig file ... Select the properties that you want to define so that IntelliJ IDEA creates stubs for them, or leave...
Read more >editorconfig | Yarn - Package Manager
Those objects will have a `notfound: true` property. All of the objects will have a `name: string` property that contains the fully-qualified file...
Read more >Add custom metadata or config to package.json, is it valid?
To read such custom properties, use the following technique: require("./package.json").org_example.random // -> true ...
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
We are good to go! Expect the pull request soon.
Would prefer to see someone make some standard config file (or folder) for all configs to live in rather than continuing to clutter package.json with xyz.
…that said, if it does get in, I’ll probably use it.