Code Monkey home page Code Monkey logo

Comments (5)

sindresorhus avatar sindresorhus commented on May 20, 2024

Here: https://github.com/sindresorhus/trash/blob/master/lib/macos.js#L10

What do you want done here?

from trash.

5punk avatar 5punk commented on May 20, 2024

@sindresorhus By any chance would you have the source code to that binary?

One of the ways we handle external file requirements is

  • Check if file exists in path
  • If not, write file to path

Then, external file requirements / executions will work :)

from trash.

sindresorhus avatar sindresorhus commented on May 20, 2024

By any chance would you have the source code to that binary?

Yes, it's linked to from the readme: https://github.com/sindresorhus/macos-trash

One of the ways we handle external file requirements is
Check if file exists in path
If not, write file to path

Please clarify. I have no idea what this means.

from trash.

5punk avatar 5punk commented on May 20, 2024

When this package is a dependency to a project that is built into a binary,
__dirname is built into /Users/5punk/projects/ProjectTest/node_modules/trash/bin/macos-trash

So when I give this built binary package to you, macos-trash is not found because it is still trying to search for the binary at /Users/5punk/projects/ProjectTest/node_modules/trash/bin/macos-trash

So a workaround is to check if the file exists in a generic path, if it doesn't exist, write the source code to the generic path.

const BINARY_PATH = isWindows ? '\AppData\trash\macos-trash' : '/opt/trash/macos-trash';

if (!fileExists(path.resolve(BINARY_PATH)) {
  fs.writeFileSync(BINARY_PATH, TRASH_SOURCE_CODE.toString());
  // make it or built it next (clang)
}

// Now feel free to use it :)
var bin = BINARY_PATH;

better yet, just download the release package (.zip) from
https://github.com/sindresorhus/recycle-bin/
https://github.com/sindresorhus/macos-trash

and then, run the build script and now you've binaries at the location you want. :)

from trash.

sindresorhus avatar sindresorhus commented on May 20, 2024

I'm willing to move the require statements to the top as that's a better practice anyways, but I'm not interested in adding lots of workarounds for this. nexe should just do what Electron does and monkeypatch fs and child_process so it just works transparently: https://github.com/electron/electron/blob/master/docs/tutorial/application-packaging.md#node-api

from trash.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.