Transformer & Dependency Compilation Error
54 Replies
Can you post your tsconfig
and package.json
tsconfig.json
Solution

here is your problem
I advise you to simply remove them

I use noUncheckedIndexAccess all the time, but I don't use noUnusedLocals, tend to use eslint for things like that
Hm, let me try disabling noUnusedLocals
Those errors seem to be gone now. I gotta fix a few unrelated ones and then see if the game builds just fine
I need to remove the tsconfig.build.json from my template lol
its not needed anymore
usually you first see syntax errors from typescript after all the transformers have finished running, after which you may see errors from
roblox-ts
itselfYep, seems like the typescript errors are dealt with. The current ones are
error TS roblox-ts:
Thanks a ton for the help. I'll mark this as solved in a bit once the game builds (just to make sure)
Hey @iSentinel, is typescript-eslint/no-unused-vars
enabled by default in your eslint config?yes
Disabling noUnusedLocals in
tsconfig.json
seems to have completely removed all warnings of itunder:
Eslint isn't logging it, either
It's just grayed out

That's odd, even directly specifying no-unused-vars in
eslint.config.json
does nothing...

Can you run 'npx @eslint/config-inspector' and see the state of the rule?
Sure
Never used the inspector before, but do you mean this? Filtered for the specific file shown in the screenshot

Seems to be enabled
Full screenshot

Yes, just wanted to make sure it was enabled
I'll have a look later and see if it works on my end still
What version of my config are you on
1.0.0
Seems latest is 1.2.6, should I upgrade?
Could be worth trying
But you might get a few eslint errors
XD
Haha, let's see
It's fixed!
That's an awesome rule

š
A few is a bit of an understatement
Ah, didn't mean to ping on reply
its cool i prefer it
So do I
Ah you're talking about the ping?
I meant the new rules
the ping
š
Haha
I just need to go through and figure out perf at some point, its a bit slow at times
Never really noticed any delays, to be honest
Might be different for massive codebases, though?
It can be. My machine is fine with it, but fresh-runs can be slower. Running npx eslint in my previous project could take ~15s
I think spell checking was like a 1/3rd of that
Jeez
How large was your previous project?
Sentinel, did you enforce arrow-parens in the latest updates?
err, reasonably, it was a lot of react code, but nothing like giganstic either
As in like function((x) => {}?
Yep
Yes
I kind of prefer not having them when not needed
But at the same time
It makes adding new params harder for example
That's fair
Since you have to go add them in just to add a new arg
I guess it's aesthetic vs practicality
Yeah, so it's trying to find a balance
And in the end I just decided it wasn't worth it and if anything it was less consistent
I agree with consistency, but it also feels a lot cleaner doing something like
const x = function(object => {})
Looks a bit more difficult to read with the parenthesis
I'll probably just disable it
if i can find the ruleIt's in prettier
Under "arrowParens: "always","
You should just be able to, in the config, set prettier under "formatters" with that option
and then it'll only override the option you gave
Yep, all done
Thanks
np!