I'm a developer, product manager and public speaker based in the SF Bay Area. I'm passionate for JavaScript, the web, hackathons, teaching, photography & cocktails.
In this case it doesn't make a difference whether @types/emojione is a dev dependency or not because the .d.ts will only expose one signature that has only built-in types. But if we would have a function that for example exposes a Buffer as part of one signature and we would need @types/node as a normal dependency since the generated .d.ts file has a connection to it. So the best practice would be to just do it for all dependencies that you actually use during runtime.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In this case it doesn't make a difference whether
@types/emojioneis a dev dependency or not because the.d.tswill only expose one signature that has only built-in types. But if we would have a function that for example exposes aBufferas part of one signature and we would need@types/nodeas a normal dependency since the generated.d.tsfile has a connection to it. So the best practice would be to just do it for all dependencies that you actually use during runtime.