Skip to content

Conversation

@meteor-ioi
Copy link

The pkg.assets configuration in package.json was pointing to a non-existent controller/public directory. This commit updates the path to decktap-web/dist/**/*, which is the correct output directory for the web application's build process. This change ensures that the web interface assets are included in the packaged executable, allowing the application to function correctly when built for Windows using pkg.

The `pkg.assets` configuration in `package.json` was pointing to a non-existent `controller/public` directory.
This commit updates the path to `decktap-web/dist/**/*`, which is the correct output directory for the web application's build process.
This change ensures that the web interface assets are included in the packaged executable, allowing the application to function correctly when built for Windows using `pkg`.
@Rico00121
Copy link
Owner

Have you tested the new build after packaging to simulate keyboard operations normally?

@Rico00121
Copy link
Owner

Judging from what I have learned so far, using pkg packaging destroys the ability of nut-js to call the system native interface (this is why I removed pkg-related configuration on the main branch). So at the moment you can only run the project directly from the project using nodejs, and I will try to build the project using electron to solve the problem later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants