You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of using the named path replacements with the @ prefix, provide the ability to match paths without them, e.g.:
constpath=require('@nodewell/path')// instead of this...path('@src/**/*.*')// ...use like thispath('src/**/*.*')
leaving the @ prefix is optional, the paths can be used with or without the @ prefix
the '@' alone will always mean the root directory (or the configured root)
leaving the @ prefix in the path config file is also a possibility, e.g.: instead of "@src": "./src", it's possible to define custom paths like this: "src": "./src"
in the config files, path values can be used too without the @ prefix, e.g.: instead of "images": "@assets/images", use like this: "images": "assets/images"
add a config option for this feature in the .pathsrc file
The text was updated successfully, but these errors were encountered:
Instead of using the named path replacements with the
@
prefix, provide the ability to match paths without them, e.g.:@
prefix is optional, the paths can be used with or without the@
prefix'@'
alone will always mean the root directory (or the configured root)@
prefix in the path config file is also a possibility, e.g.: instead of"@src": "./src"
, it's possible to define custom paths like this:"src": "./src"
@
prefix, e.g.: instead of"images": "@assets/images"
, use like this:"images": "assets/images"
config
option for this feature in the.pathsrc
fileThe text was updated successfully, but these errors were encountered: