cannot find type definition file for 'cli' in Angular 14 - angular14

In Angular tsconfig.json file showing this error.
** cannot find type definition file for 'cli'
The file is in the program because:
entry point for implicit type library 'cli' **
how to solve this problem.

Related

Error: EISDIR: File is a directory., '/node_modules/bootstrap/scss/mixins' (CodeSandbox / Bootstrap / VueJS)

I'm a bit new to all of those web techs (CodeSandbox, Bootstrap and VueJS) but I learn fast. After doing a lot of research, I wanted to start my web platform project with this project template to have a good base and a good structure but I'm stuck with this error :
Cannot find module 'bootstrap/scss/mixins' from '/src/styles'
And when I look in the file containing the "import" directive :
Error: Error: EISDIR: File is a directory., '/node_modules/bootstrap/scss/mixins'
on line 10:9 of node_modules/bootstrap/scss/bootstrap.scss
from line 10:2 of /stdin
>> #import "mixins";
I understand that "mixins" is a directory, okay, but it's the bootstrap code man... I cannot change it on codesandbox and after checking on bootstrap github's repository, it seems normal that "mixins" is a directory.
You can check the code sandbox here (no changes made, project just imported, modules not updated, I tried but it changed nothing). The file containing all import directives is src/styles/themes.scss direct link.
Thanks by advance for your help ! :)

is there a way to open a file in webpack browser extension application

When compiling my browser extension project I have this error :
Module not found: Error: Can't resolve 'fs' in 'C:\Users\admin\project\node_modules\pdf-table-extractor'
I'm using webpack and npm.
pdf-table-extractor is an npm library that extracts pdf data in Json format.
This library require the fs library to open the pdf file path.
It seems that this library is somehow blocked by webpack.
Can any one help with this ?
Adding
node: {
fs: 'empty'
}
to the "webpack.config.js" file solve the compiling error but the extension is failing in the browser.
Many thanks in advance.

IntelliJ not registering file type with correct plugin

Edit: Making title more generic as this situation could apply to any file type.
I am brand new to Puppet and was given the task of adding a new Puppet configuration file. I added a new file, but it either contained a syntax error, had the wrong extension or both (I don't remember), and I believe that caused the file to not register with the plugin. However, even after fixing the syntax error and ensuring the .pp extension, the file is not registering. If I add a new .pp file, it registers right away.
I tried deleting the file and adding it again, but it still won't register, which leads me to believe there is a metadata file somewhere keeping track of which files to register and which to ignore.
I've looked through the the .idea folder for mentions of the file but all I see are entries in the workspace.xml under the ChangeListManager and FileEditorManager.
I also tried cloning the repository again but it still doesn't register. Any ideas?
As it turned out, the entire file name had somehow been associated with a text file.
File -> Settings -> File Types -> Recognized File Types -> Text
Located the file name and removed it. The file registered as a Puppet file.

IntelliJ changes file type

I am having a quirky intellij problem.
I have a folder with a bunch of json files. When I add a specific json with name
LocalValueCode.json . InteliJ changes the file type to .file .
This only happens with this file specific filename. In file associations settings I have *.json as a pattern for my json files.
Has anyone encountered this issue before?
You need to go to Settings | Editor | File Types and make sure that this name is not associated with any incorrect file type.
I had a similar problem with a YAML file. I created the file but accidentially made it a text-type file. Then when creating YAML content in that file there was no syntax highlighting. Additionally, a bar was shown on the upper edge of the editor window stating that there are plugins for the file extension *.yml -- of which I had already one installed that worked perfectly with other YAML files.
A grep on the $HOME/.IdeaIC2018.3 directory with that filename found the .IdeaIC2018.3/config/options/filetypes.xml file that contained the following line:
<mapping pattern="cassandra-docker.yml" type="PLAIN_TEXT" />
After removing that line and restarting IntelliJ the YAML file was correctly recognized as YAML.
I just had this problem and I have an better answer, I'm leaving here for whomever might have the same issue.
If you go to Preferences > File types > Recognized file types (Text) > Registered patterns, you will find the file there registered as an association. Just remove the association and you should be fine.

Cannot use TSC - Error reading file "anything.ts": File not found

No matter what I do I cannot get the TSC Typescript compiler to find any files. I have tried both the tsc that comes with the Visual Studio Extension and the one that comes from npm. I've tried in the Node.js command line windows shell, and the Git Bash shell. No matter what I do, it just says the file is not found. I've read that the compiler will only work for .ts and .str files, but that does not seem to be the problem.
Here is a quick example of what I'm seeing. I know these files will be empty, but I've tried all of this with files containing code and it doesn't change anything.
C:\>touch test.ts
C:\>ls *.ts
test.ts
C:\>tsc test.ts
Error reading file "test.ts": File not found
C:\>tsc C:\test.ts
Error reading file "C:\test.ts": File not found
C:\>touch test.str
C:\>tsc test.str
Error reading file "test.str": File not found
C:\>tsc ./test.str
Error reading file "./test.str": File not found
C:\>tsc ./test.ts
Error reading file "./test.ts": File not found
C:\>touch test.js.ts
C:\>tsc test.ts
Error reading file "test.ts": File not found
C:\>tsc test.js
Error reading file "test.js": File not found
I'm afraid, that TSC fails that way on empty files.
Looks like a bug in the current compiler [0.8], tsc shouldn't fail on empty files. However
I know these files will be empty, but I've tried all of this with files containing code and it doesn't change anything.
I'm a bit worried about this part. Is that still the case?
That's difficult to debug from afar. The typescript compiler does quite a lot of processing until it resolves a file.
What's the output of running
tsc -debug test.ts
? Also, please make sure that test.ts is non-empty.