node-app-root-path
node-app-root-path copied to clipboard
inxilpro
Determine the root path to your project
I try using the lib in my project to fix Windows builds via GitHub actions. Otherwise my projects build fine. Seems like the lib isn't compatible with ES modules setup......
This may be related to #49 , but given the original ticket was not about esbuild, this is more related to one of the replies there. I'm using `serverless-esbuild` /...
When deploying servererless insto Google Cloud functions - the app root reported is incorrect. ```nodejs const appRoot = require("app-root-path"); console.log(appRoot.toString()); ``` `/layers/google.nodejs.functions-framework/functions-framework/node_modules/@google-cloud/functions-framework/build/src` ```nodejs console.log(__dirname); ``` `/workspace` I'm not sure where...
- it is not necessary to use __dirname if APP_ROOT_PATH env var is used. - this should solve a problem when the package is used in an ESM app.
Hey, Currently the package is not compatible with yarn workspaces/lerna. Example of issue you can find here: https://github.com/typeorm/typeorm/issues/2805 Is there any way to support yarn workspaces/lerna for monorepo solutions? Regards,...
I only noticed this today when changes in `globby` starting throwing path errors, so might have been there a while and I just didn't notice. Under node v11, working in...
Current resolver detects Yarn Plug 'N' Play but [resolves](https://github.com/inxilpro/node-app-root-path/blob/54d06fef2340a36070fbfc24973bb676079aa7a1/lib/resolve.js#L61) app root path to repo root, but in the context of a monorepo structure, it may be desirable to have app...
Hosted a node application on Azure as Web App which is using app-root-path library to resolve the file paths. It is resolving to iisnode directory which is the node handler...
Browserify 16.5.0 does not seem to provide a `.main` property on the `require` object, so requiring app-root-path is failing because browser cannot read property `.filename` from `require.main` (which is `undefined`)...
I strongly believe `appRoot.resolve` should behave as `path.resolve` does. It means: - given relative path, resolve absolute path relative to the app root - given absolute path, resolve given absolute...
