jinder / path

NodeJS 'path' module

path

This is an exact copy of the NodeJS ’path’ module published to the NPM registry.

Documentation

Install

$ npm install --save path

License

MIT

path's Issues

Path add a /bin

Hello,

More than issue is a question , when I use the path package in my nodejs server (express) example: path.resolve('./public/index.html') , I dont know why package path adds /bin in my route.

The path should be '.../public/index.html' and with de path package '.../bin/public/index.html'

I'm using a nodejs , with reverse proxy Nginx.

Do u know why happen?

Regards.

NPM@3 causes unwanted module overwrite

Before NPM version 3.0.0, I could use modules that require()'d this module, and then go ahead and use the Node core path module all I wanted. But now in NPM@3, the entire dependency tree is installed as flat as possible in the node_modules folder. This means that if I use a module that uses this module, I can no longer use the native path module anymore, because this one overwrites it. I did not put this module in my package.json as a dependency, an yet I am forced to use it. This should NOT be possible. If it's important to provide mirrors of the Node core modules in NPM, they should be under a different name. This wouldn't cause any problems, but it would solve this one.

install documentation

The current installation instructions for this package are to type the following:

npm install --save path

However, the package installs when you type the following:

npm install path --save

Can't add path that contains "@"

Hi

I just found out that if you do:

path.join("dir1", "@dir2");

It fails... :)

No Documenttaion

Missing documentation on npmjs.com and here on github too. Please add it. I was searching the purpose of this dev and found nothing.

[email protected] asking for write and publish access

Someone has been emailing me from [email protected] asking for write and publish access to the repo and npm module.

I don't even know if I still have access, but in light of recent events, and considering that I don't know the person personally, I've said no - he can PR and we'll review it, and he's persisted that he wants write and publish access.

I just want to document that here because I don't know if it's the real Tony Mobily or not, and it seems that kind of conversation should have come up as an issue first - and I don't see any activity from him here.

My suggestion is that we don't give anyone new access as this is an obvious target for supply chain vulnerability and anyone writing new code should probably be using the path functions available via new URL(), in most cases.

Publish as standard JS modules?

It would be very useful for code that runs in browsers and Node to have this package available as standard JS modules.

I realize that the package seems unmaintained at this point, but maybe there's someway this could be contributed.

Is this NPM package required when NodeJS ships with a path module?

Why would anyone need to install this module when it comes bundled with npm?

Adding active maintainers?

Could new maintainers be added to the project so that PRs could be accepted and new versions published to npm?

how are you

When used in Angular will introduce the value of the base attribute unexpectedly

See this SO issue:

https://stackoverflow.com/questions/59605333/not-using-the-base-attribute-when-making-domsanitizer-api-calls

BUG: Can't join paths that starts with '..'

Steps to reproduce:

1. Call path.join("/root", "../something")
2. Returns something

Expected result:

1. Should return /root/../something

path.resolve will add prefix / in windows

In windows 10 edge browser, all resolve result will prefix /
e.g 1

path.resolve('', 'C:/<path>') 

will get

/C:/<path>

it suppose to get

C:/<path>

e.g 2

path.resolve('C:/<path>', 'a/b/c') 

will get

/C:/<path>/a/b/c

it suppose to get

C:/<path>/a/b/c

Does not work in phantomjs: process is undefined

This module implicitly depends on process, which isn't defined outside of Node. Prior to a2f87c3, this module had an extra var process = process || {}; in path.js that allowed the use of functions that don't meaningfully rely on process.

And since it sounds like people shouldn't be using this module in Node itself (#6), this problem might affect most legitimate users of this module.

See philc/vimium@da57280 for an example of a legitimate use of this library that was broken by the removal of var process = process || {};.

Please update to Node v0.12

The path module got some new additions in Node v0.12. It would be great to add them to this package for consistency and feature-parity.

• path.win32
• path.posix
• path.parse()
• path.format()

MAKE EN ERROR SO MY FRIEND DOSNT RANDOMLY IMPORT IT

HE SUCKS AT CODING

cannot configure webpack to correctly resolve @ in path in MacOS X

1)my config.js

`'use strict'
'use strict'
const path = require('path')
const utils = require('./utils')
const config = require('../config')
const vueLoaderConfig = require('./vue-loader.conf')
var PostCompilePlugin = require('webpack-post-compile-plugin')
var TransformModulesPlugin = require('webpack-transform-modules-plugin')

function resolve (dir) {
return path.join(__dirname, '..', dir)
}

const createLintingRule = () => ({
test: /.(js|vue)$/,
loader: 'eslint-loader',
enforce: 'pre',
include: [resolve('src'), resolve('test')],
options: {
formatter: require('eslint-friendly-formatter'),
emitWarning: !config.dev.showEslintErrorsInOverlay
}
})

module.exports = {
context: path.resolve(__dirname, '../'),
plugins: [
// ...
new PostCompilePlugin(),
new TransformModulesPlugin()
],
entry: {
app: './src/main.js'
},
output: {
path: config.build.assetsRoot,
filename: '[name].js',
publicPath: process.env.NODE_ENV === 'production'
? config.build.assetsPublicPath
: config.dev.assetsPublicPath
},
resolve: {
extensions: ['.js', '.vue', '.json'],
alias: {
'vue$': 'vue/dist/vue.esm.js',
'@': resolve('src'),
'jsencrypt$':'jsencrypt/bin/jsencrypt.min.js',
'$common': path.resolve('src/common')
}
},`

2)npm run dev
3) error
these dependencies were not found:

• @/views/Meeting/MeetingRoomList in ./src/router/modules/meeting.js
• @/views/Meeting/applyList in ./src/router/modules/meeting.js
• @/views/Meeting/meetingAdd in ./src/router/modules/meeting.js
• @/views/Meeting/meetingDetail in ./src/router/modules/meeting.js
• @/views/Meeting/meetingEdit in ./src/router/modules/meeting.js