ERRO BOOSTRAP ANGULAR

05/01/2019

0

Boa noite alguém sabe como resolver este problema no angular?

C:\\cms>ng serve
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
91% additional asset processing scripts-webpack-plugin× 「wdm」: Error: ENOENT: no such file or directory, open 'C:\\cms\\node_modules\\bootstrap\\dist\\css\\booststrap.css'
at Object.openSync (fs.js:439:3)
at Object.readFileSync (fs.js:344:35)
at Storage.provideSync (C:\\cms\\node_modules\\enhanced-resolve\\lib\\CachedInputFileSystem.js:98:13)
at CachedInputFileSystem.readFileSync (C:\\cms\\node_modules\\enhanced-resolve\\lib\\CachedInputFileSystem.js:259:32)
at Observable.rxjs_1.Observable.obs [as _subscribe] (C:\\cms\\node_modules\\@ngtools\\webpack\\src\\webpack-input-host.js:35:51)
at Observable._trySubscribe (C:\\cms\\node_modules\\rxjs\\internal\\Observable.js:44:25)
at Observable.subscribe (C:\\cms\\node_modules\\rxjs\\internal\\Observable.js:30:22)
at SyncDelegateHost._doSyncCall (C:\\cms\\node_modules\\@angular-devkit\\core\\src\\virtual-fs\\host\\sync.js:22:20)
at SyncDelegateHost.read (C:\\cms\\node_modules\\@angular-devkit\\core\\src\\virtual-fs\\host\\sync.js:49:21)
at WebpackCompilerHost.readFileBuffer (C:\\cms\\node_modules\\@ngtools\\webpack\\src\\compiler_host.js:124:44)
at VirtualFileSystemDecorator.readFile (C:\\cms\\node_modules\\@ngtools\\webpack\\src\\virtual_file_system_decorator.js:39:54)
at Promise (C:\\cms\\node_modules\\@angular-devkit\\build-angular\\src\\angular-cli-files\\plugins\\scripts-webpack-plugin.js:92:49)
at new Promise (<anonymous>)
at scripts.map.fullPath (C:\\cms\\node_modules\\@angular-devkit\\build-angular\\src\\angular-cli-files\\plugins\\scripts-webpack-plugin.js:91:24)
at Array.map (<anonymous>)
at hook (C:\\cms\\node_modules\\@angular-devkit\\build-angular\\src\\angular-cli-files\\plugins\\scripts-webpack-plugin.js:90:43)
Joao Velozo

Joao Velozo

Responder

Posts

11/01/2019

Joel Rodrigues

Fala, João. Beleza?

Experimente apagar a pasta node_modules e depois rode o "npm install" de novo.
Responder

Utilizamos cookies para fornecer uma melhor experiência para nossos usuários, consulte nossa política de privacidade.

Aceitar