# Primitive Types

**URL:** <https://forum.codewithmosh.com/t/primitive-types/15082>\
**Category:** JavaScript\
**Created:** [September 12, 2022, 1:14am UTC](https://forum.codewithmosh.com/t/primitive-types/15082 "2022-09-12T01:14:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![FatherDeacon](https://avatars.discourse-cdn.com/v4/letter/f/94ad74/32.png) [@FatherDeacon](https://forum.codewithmosh.com/u/FatherDeacon)\
**Post date:** [September 12, 2022, 1:14am UTC](https://forum.codewithmosh.com/t/primitive-types/15082/1 "2022-09-12T01:14:28Z")

</div>

I have watched this short clip, however when Mr Mosh enters the code attatched, why is there a scratch?

 ![Name strike error](https://us1.discourse-cdn.com/flex020/uploads/codewithmosh/original/2X/2/2bd5018a7874ea16e2620c75cadf640af863debb.jpeg)

---

<div class="post-metadata">

**Author:** ![jmrunkle](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.codewithmosh.com/jmrunkle/32/3765_2.png) [@jmrunkle](https://forum.codewithmosh.com/u/jmrunkle)\
**Post date:** [September 12, 2022, 1:41am UTC](https://forum.codewithmosh.com/t/primitive-types/15082/2 "2022-09-12T01:41:45Z")

</div>

He has not saved yet, so I am not sure what is in the saved file in that screenshot. It is most likely just the linter lagging behind the input. If you type the same into your VSCode and then save the file, do you still get a strike through?

---

<div class="post-metadata">

**Author:** ![jmrunkle](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.codewithmosh.com/jmrunkle/32/3765_2.png) [@jmrunkle](https://forum.codewithmosh.com/u/jmrunkle)\
**Post date:** [September 12, 2022, 4:29am UTC](https://forum.codewithmosh.com/t/primitive-types/15082/3 "2022-09-12T04:29:45Z")

</div>

OK, I just tried typing the same into my own instance of VSCode and it looks like it thinks that the `name` variable is a deprecated keyword of some kind (coming from the typescript). If you hover over it, you can see what the error message says:

> ‘name’ is deprecated.ts(6385)

Then it has a pointer to a specific file defining some types and marking `name` as deprecated. Looking this up elsewhere led to this: [Reddit - Dive into anything](https://www.reddit.com/r/vscode/comments/ltonp7/name_is_deprecated_ts6385/)

I think basically this is just a nuisance caused by typescript linting and can be ignored. Alternatively you can follow the advice in that Reddit post.

---

<div class="post-metadata">

**Author:** ![FatherDeacon](https://avatars.discourse-cdn.com/v4/letter/f/94ad74/32.png) [@FatherDeacon](https://forum.codewithmosh.com/u/FatherDeacon)\
**Post date:** [September 12, 2022, 4:30am UTC](https://forum.codewithmosh.com/t/primitive-types/15082/4 "2022-09-12T04:30:59Z")

</div>

Yes, unfortunately I am getting the following error:

 ![Untitled](https://us1.discourse-cdn.com/flex020/uploads/codewithmosh/original/2X/a/a459323e07bd4b483fa3a908fe918bf1ac5e7d50.png)

---

<div class="post-metadata">

**Author:** ![FatherDeacon](https://avatars.discourse-cdn.com/v4/letter/f/94ad74/32.png) [@FatherDeacon](https://forum.codewithmosh.com/u/FatherDeacon)\
**Post date:** [September 12, 2022, 4:34am UTC](https://forum.codewithmosh.com/t/primitive-types/15082/5 "2022-09-12T04:34:00Z")

</div>

Couldn’t I by pass and assign a variable as (let important\_name).

I wouldn’t think it would make a difference. After all it is only assigning “important\_name as a variable”.

---

<div class="post-metadata">

**Author:** ![jmrunkle](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.codewithmosh.com/jmrunkle/32/3765_2.png) [@jmrunkle](https://forum.codewithmosh.com/u/jmrunkle)\
**Post date:** [September 12, 2022, 4:37am UTC](https://forum.codewithmosh.com/t/primitive-types/15082/6 "2022-09-12T04:37:25Z")

</div>

Yep, but if you needed to use `name` in the global namespace, you can probably just ignore the warning.