You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should search at first before submitting a new one.
Please read this entire template before posting any issue. If you ignore these instructions
and post an issue here that does not follow the instructions, your issue might be closed,
locked, and assigned the not reproducible label.
🐛 Bug Report
This started appearing when updated to last version
No inputs were found in config file 'c:/**/node_modules/@elastic/elasticsearch/tsconfig.json'. Specified 'include' paths were '["./src/**/*.ts"]' and 'exclude' paths were '["node_modules"]'.ts
@elastic/enterprise-search": "^8.6.1",
To Reproduce
Steps to reproduce the behavior:
run npm i @elastic/enterprise-search within typescript project
VS code shows this error
Expected
Not to show error its a bit annoying
Your Environment
node version: v20.17.0
@elastic/enterprise-searchversion: >=8.6.1
os:Windows
VS Code
The text was updated successfully, but these errors were encountered:
It's not uncommon that somebody already opened an issue or in the best case it's already fixed but not merged. That's the reason why you should search at first before submitting a new one.
Please read this entire template before posting any issue. If you ignore these instructions
and post an issue here that does not follow the instructions, your issue might be closed,
locked, and assigned the
not reproducible
label.🐛 Bug Report
This started appearing when updated to last version
@elastic/enterprise-search": "^8.6.1",
To Reproduce
Steps to reproduce the behavior:
npm i @elastic/enterprise-search
within typescript projectExpected
Not to show error its a bit annoying
Your Environment
@elastic/enterprise-search
version: >=8.6.1The text was updated successfully, but these errors were encountered: