-
Notifications
You must be signed in to change notification settings - Fork 3
OSOE-430: Support a single NE instance per solution on Linux, too, in Lombiq.NodeJs.Extensions #74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Note the last commit (6d8e166) that contains the fixes to various ESlint warnings, including some that aren't related to this issue. (because the auxiliary scripts in Lombiq.NodeJs.Extensions/scripts/ that are only used by node during the compilation don't get linted automatically) |
@@ -26,7 +27,8 @@ async function copyFilesFromConfig(config) { | |||
return Promise.all(config | |||
.map((assetsGroup) => assetsGroup.sources.map((assetSource) => { | |||
// Normalize the relative path to the directory to remove trailing slashes and straighten out any anomalies. | |||
const directoryToCopy = path.normalize(assetSource); | |||
const projectPath = getProjectDirectory(); | |||
const directoryToCopy = path.normalize(path.join(projectPath, assetSource)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
path.resolve()
seems a better choice to me instead of path.join()
in case of absolute assetSource
const sourceAndTargetPaths = [pathPattern, assetsGroup.target]; | ||
const targetPath = (process.platform === 'win32') | ||
? assetsGroup.target | ||
: path.normalize(path.join(projectPath, assetsGroup.target)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
path.resolve()
same reason like above.
Co-authored-by: József Horváth <[email protected]>
OSOE-430
Fixes #17