Thore Strassburg

@Seybo when u set this as ur default name it works for u? Cause it doesn't for me. As an experiment I just change the working diretory with `:cd `...

@Dbz not so far, sry.

I have the same issue, but for a different reason. Unfortunately (to my knowledge) Packer relies on Lua to dump the `config`/`setup` functions as String (and later parse them back)...

I'm working on a solution. I'm currently struggling with that `loadstring('setmetatable({ key1 = "value1" }, { __call = function(self, first_argument) print(self.key1) print(first_argument) end })')` does not fully work. The result...

Got it. Using `load(return ...)()` does the job. Update: Next issue is that `load('return loadstring(\"' .. string.dump(function() print('foo') end, true) .. '\")())` returns `nil`. Seems to be an escape issue...

Just another up-vote for this feature. Would help the developer experience so much!

@neongreen unfortunately not. I tried to do some awkward integration with [jest-image-snapshot](https://www.npmjs.com/package/jest-image-snapshot) (not do take snapshots, but for the comparison + UI part). But unfortunately their code is tightly coupled...

For me, the DX is key. Developers should not get desensibilized and get annoyed by failing visual regression tests without a good way for them to verify what has changed...

In the meanwhile, while trying to get rid of some namespaces, I realized this. If I convert the above code, it still does not recognize it as being unused. Which...

Hmm. I struggle to do so. 🙈 My approach to provide a minimal TypeScript project with everything: ```bash $ mkdir /tmp/knip-test-namespace $ cd /tmp/knip-test-namespace $ npm init $ npm add...