问题
I'm building a web app in NodeJS, and I'm implementing my API routes in separate modules. In one of my routes I'm doing some file manipulation and I need to know the base app path. if I use __dirname it gives me the directory that houses my module of course.
I'm currently using this to get the base app path (given that I know the relative path to the module from base path):
path.join(__dirname, "../../", myfilename)
Is there a better way than using ../../? I'm running Node under Windows so there is no process.env.PWD and I don't want to be platform specific anyway.
回答1:
The approach of using __dirname is the most reliable one. It will always give you correct directory. You do not have to worry about ../../ in Windows environment as path.join() will take care of that.
There is an alternative solution though. You can use process.cwd() which returns the current working directory of the process. That command works fine if you execute your node application from the base application directory. However, if you execute your node application from different directory, say, its parent directory (e.g. node yourapp\index.js) then __dirname mechanism will work much better.
I hope that will help.
回答2:
You can use path.resolve() without arguments to get the working directory which is usually the base app path. If the argument is relative path then it's assumed to be relative to the current working directory so you can write
require(path.resolve(myfilename));
to require your module at app root.
回答3:
You can define a global variable like in your app.js:
global.__basedir = __dirname;
Then you can use this global variable anywhere. Like that:
var base_path = __basedir
来源：https://stackoverflow.com/questions/21637099/app-base-path-from-a-module-in-nodejs