imlinhanchao / librejo Goto Github PK

View Code? Open in Web Editor NEW

17.0 2.0 5.0 18.66 MB

📚 图书管理网站，用于个人图书管理，支持多用户。

Home Page: https://librejo.cn/

License: GNU General Public License v3.0

JavaScript 51.49% HTML 0.34% Vue 45.17% Less 2.60% EJS 0.40%

book nodejs vue bookshelf

librejo's Introduction

librejo's People

Contributors

Stargazers

Watchers

Forkers

abceset kznmft weiling103 kryhear escape0807

librejo's Issues

二级菜单按钮失效问题

登录后点击二级菜单按钮没反应

前端调试执行npm run dev 报错

已经完成了配置，也npm install了，现在执行npm run dev出现以下的报错。
想问下作者之前遇到过类似的问题么？

> webpack-dev-server --disableHostCheck=true --content-base ./views/ --open --inline --hot --compress --history-api-fallback --config ./build/webpack.dev.config.js

× ｢wds｣: Invalid configuration object. Webpack has been initialised using a configuration object that does not 
match the API schema.
 - configuration has an unknown property 'mode'. These properties are valid:
   object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
   For typos: please correct them.
   For loader options: webpack 2 no longer allows custom properties in configuration.
     Loaders should be updated to allow passing options via loader options in module.rules.
     Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:        
     plugins: [
       new webpack.LoaderOptionsPlugin({
         // test: /\.xxx$/, // may apply this only for some modules
         options: {
           mode: ...
         }
       })
     ]
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] dev: `webpack-dev-server --disableHostCheck=true --content-base ./views/ --open --inline --hot --compress --history-api-fallback --config ./build/webpack.dev.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.