Frontmatter
| id | 1175 |
| title | Project will not build on windows machines, nothing in dist folder |
| state | Closed |
| labels | bug |
| assignees | [] |
| createdAt | Sep 10, 2020, 10:06 AM |
| updatedAt | Sep 10, 2020, 11:00 AM |
| githubUrl | https://github.com/neomjs/neo/issues/1175 |
| author | notnikola1 |
| commentsCount | 4 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Sep 10, 2020, 10:25 AM |
Project will not build on windows machines, nothing in dist folder

Hi Nick and welcome to the community!
Thx for the PR, I have not tested builds on windows in ages. It did work before adding the build programs, but this was quite a while back.
I think we don't need the new webpackResolvedPath variable.
if (process.platform === "win32") {
// due to specific windows pathing we must do a lil bit of hackery to get it to build properly
// functionality on linux/mac remains unchanged
webpack = path.resolve(webpack).replace(/\\/g,'/');
}
should do the same. I might do this minor cleanup, does not really matter though inside the build tools.

Just out of curiosity: What would happen in case you are using Windows, but with a Linux Kernel? This might require slashes instead of backslashes again.
Well, I am definitely not a Windows guy, so no clue.

yeah, you're right, its just a habit from years of working in my current company to declare a new variable always rather than using the old one.
///
as for the linux kernel, are you referring to the linux subsystem that is on windows 10?
honestly, i wouldn't know, i never used it, i actually dual boot between linux and windows when i need to : /
On Thu, Sep 10, 2020 at 10:43 AM Tobias Uhlig notifications@github.com wrote:
Just out of curiosity: What would happen in case you are using Windows, but with a Linux Kernel? This might require slashes instead of backslashes again.
Well, I am definitely not a Windows guy, so no clue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/neomjs/neo/issues/1175#issuecomment-690086887, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH3DUWWCUNTZITUOWKXPYODSFCGRHANCNFSM4REQEALQ .

Meant this one: https://linuxhint.com/linux_kernel_windows10/
Well, let's assume using it changes process.platform in node. If not, there will be a new ticket for sure.
Feel free to jump into the Slack Channel in case you have any questions on neo in general. The vdom concept can be a bit confusing at first.
Best regards, Tobias
Describe the bug There is no working build on windows machines.
To Reproduce Steps to reproduce the behavior:
Expected behavior The project builds correctly with all the code and CSS
Desktop (please complete the following information):
Additional context Windows has specific path resolving issues that are not addressed