Question:
When writing about the running of the project, the problem of joi. Validate is not a function appears
#Reason:
After checking, it is possible that the third-party module joi was not downloaded or the version is wrong
solve:
Open the PowerShell and uninstall the joi if it has been downloaded:
npm uninstall joi
Then download the module again, joi:
npm install joi
Node rerun project
After installing nodejs, run NPM on the command line and report error: cannot find module ‘internal/util/types’
The error is shown in the figure below:
Solution: delete the directory "C: users, WLS, appdata, roaming, NPM, node"_ NPM folder under modules
Error in starting node project
UnhandledPromiseRejectionWarning: MongoError: not authorized on elm to execute command { insert: “hongbaos”, ordered: false, $db: “elm” }
The reason is that you do not have permission to connect to the database
The reason is that the database mongo.conf There is an auth = true solution
1. Comment out auth = true
2. Enter adimn to set the user name and password, and use the user name and password to access the database
Switch use admin before creating user
db.createUser(
{
user:"root",
pwd:"123456",
roles:[{role:"root",db:"admin"}]
}
);When using the webpack build file project, a dist directory is generated every time. Sometimes, all the old files in the dist directory need to be deleted,
In addition to the RM – RF / dist / command, you can also use the rimraf / dist / command
The function of rimraf is to package the RM - RF command in the form of package to delete files and folders, regardless of whether the folder is empty or not
Local installation: NPM install rimraf — save dev
Global installation: NPM install rimraf – G
Use: rimraf & lt; path & gt; [& lt; path & gt;…]
api：rimraf(f, [opts], callback)
An error is as follows
checked online related:
.
because package json file does not have to configure the build script, so the above error!
Solutions:
1. Add build script to scripts in package.json:
{
"scripts": {
"build": "cross-env NODE_ENV=production webpack --config webpack.config.js"
}
}
“NODE_ENV” : user-defined environment variable
webpack “: integrated packaging command
“>config” : config file
“webpa>onfig.js” : config file, which is a Node. js module that returns a JSIN-formatted configuration information object, or the –config option to specify the configuration file
It is possible that ‘cross-env’ is not an internal or external command and is not a executable program
can be resolved by NPM I –save-dev cross-env.
The results of
Execute NPM run build, and the results will appear in the dist folder. Successful packaging!
Reference: https://www.cnblogs.com/tugenhua0707/p/9780621.html
https://www.cnblogs.com/eyunhua/p/6507100.html
Perform the following query in MYSQL Workbench
ALTER USER ‘root’ @’ localhost ‘IDENTIFIED WITH mysql_native_password BY’ password ‘
when root is USER localhost of your url, and password is your password
, then run the following query to flush privileges:
flush privileges;
try using node connections after completion.
if that doesn’t work, try @’ localhost ‘
Assume that this is a url http://localhost:8080/a/b/c?a=1&
protocol: ‘HTTP:’,// protocol
host: ‘localhost:8080’,
port: ‘8080’,// port
hostname: ‘localhost’, domain
hash: ‘#abcd’,
search: ‘?a=1& B = 2 ‘,
query: ‘a = 1 & amp; B =2 ‘,
pathname: ‘/a/b/c’,
path: ‘/a/b/c?a=1& B = 2 ‘,
href: ‘http://localhost:8080/a/b/c?a=1& B = 2 # ABC ‘
Url.parse () can break a complete URL into many parts, such as host, port, Pathname, path, and Query
var http = require("http");
var url = require("url");
var server = http.createServer(function(req,res){
var pathname = url.parse(req.url).pathname;
var query = url.parse(req.url).query;
console.log("patname:"+ pathname);
console.log(query);
res.end();
});
server.listen(80,"127.0.0.1");
NVM is installed under ~/. NVM is not installed with the previous one. I am a little obsessive, so I want to uninstall the previous one
Homebrew installed
brew uninstall node
The official website downloads the PKG installation package
A command
sudo rm - rf/usr/local/{bin/{node, NPM}, lib/node_modules/NPM, lib/node, share/man/*/node. *}
It was installed in another way
Make a script, the need to delete the file, a shuttle all kill
It will be called: uninstallNode. sh
#!/bin/bash
lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom \
| while read i; do
sudo rm /usr/local/${i}
done
sudo rm -rf /usr/local/lib/node \
/usr/local/lib/node_modules \
/var/db/receipts/org.nodejs.*Modify file permissions chmod 777 uninstallnodejs.sh
is executed on the command line
When you're done deleting all that stuff, you're done deleting node.
but there are a lot of node-based installed software and command-line tools that need to be reinstalled, such as react-native, supervisor,pm2 etc
need to delete the files under /usr/local/bin, actually they are just soft connections, it's all under /usr/local/lib/node_modules/.
was removed in the previous step, but you can still find it by pressing the TAB key because these soft connections still exist
}});
The scenarios in which this problem occurs vary, but the solutions are basically the same. This article takes lodash module as an example
Cannot find module lodash appears after the pull code is run, usually someone else USES a plug-in lodash, but you do not have it in your local environment, you can directly go to the package. Json to check if there is lodash, if there is, that proves that you do not install the lodash, use CNPM install to install it. Json package.json not found, Cannot find module lodash, global search under the file lodash, if the file is not used, then delete node_module, re-use CNPM install can be installed; Json . Just ask the relevant person to submit it, and then refer to step 1. Json, node_module package-lock. Use NPM cache clean --force to clear the cache. Then use NPM install to install. Json copy a copy of packing-lock-. jsoncopy a copy of packing-lock. jsoncopy a copy of packing-lock. json copy a copy of packing-lock-. (Of course, if the file is u update status, then don't bother, check the update content, and then submit it)
(node:57300) UnhandledPromiseRejectionWarning: Error: Can't set headers after they are sent.
at validateHeader (_http_outgoing.js:491:11)
at ServerResponse.setHeader (_http_outgoing.js:498:3)
In the Node project, you encountered this error while doing module splitting.
is checked to be package.json deleted
"babel-preset-env": "1.3.2",
"babel-preset-es2015": "6.24.1",
"babel-preset-stage-2": "6.24.1"
These three modules cause these three modules not to be deleted.
is originally required by the server to render the json inside the reference file is relative. Node_modules relative to the root directory, so the items below the root directory are related to modules such as vue, Babel-Polyfill, etc.