node-auto-launch: Be more flexible on path value: must be absolute if not Windows Store target

The target platform(s) the problem occurs on (Linux, Mac, Mac App Store, and or Windows): Windows Store
Node version (run node -v): v12.18.3
auto-launch version: 5.0.5
The options you’re passing to auto-launch: name, path
Are you using NW.js or Electron?
- If so, which version?: 11.1.1 (latest as of now)
- If you’re using Electron, are you using auto-launch from the main process or a renderer process? main
Can you reproduce this with a simple Hello World example app? yes
If needs be, would you be able to provide us with a simple app (as simple as possible) which reproduces the problem?

We are trying out a test to see how this works for Windows Store but we’re getting an error: path must be absolute

  const autoLaunch = new AutoLaunch({
    name: 'OurApp',
    path: 'explorer.exe shell:AppsFolder\\OurCompany.OurApp_abcd123456!OurCompany.OurApp',
  });

// The error throws immediately: 'path must be absolute'

We followed the instructions in the docs. Any help would be appreciated!

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 19 (4 by maintainers)

Most upvoted comments

I just setup automatic publishes to npm when releases are published on github.

To release, create a tag and release with the same name (semver version number) as seen here:

You can release to a beta channel on npm by adding -rcX to the end of the release version. If you don’t add -rcX it will release to production. Please take care when making releases that you use the correct version numbers.

Ping me if you want to release to production.

4ver on Feb 27, 2024

I’ll add a ghaction to build and publish to npm today 👍

@Oxalin I am trying to install from github with npm i Teamwork/node-auto-launch but getting error when trying to use it:

There’s no dist directory pushed to github so installing the package from gh won’t work.

4ver on Feb 26, 2024

This may answer your request, I’ll have a look this weekend: https://docs.npmjs.com/updating-your-published-package-version-number

On Fri, Feb 23, 2024 at 1:46 PM Alexandre Demers < @.***> wrote:

Once the source code is updated, I have no clue on how to update the information on npmjs. If someone can point me in the right direction, it will be a pleasure to update it.

I also have a new major version on my boiling plate which will get rid of CoffeeScript, have better code coverage and add new functionalities. I’m almost ready to merge it and it could be added as a beta version on npmjs for test purposes in the same way.

On Sat, Feb 10, 2024 at 2:00 PM Jan Hovancik @.***> wrote:

@Oxalin https://github.com/Oxalin npm installs 5.0.6 , will you please update? https://www.npmjs.com/package/auto-launch

— Reply to this email directly, view it on GitHub https://github.com/Teamwork/node-auto-launch/issues/105#issuecomment-1937096480, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACKBM4NULBHYEE6F54GLETYS67WXAVCNFSM4V4ESJXKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJTG4YDSNRUHAYA . You are receiving this because you were mentioned.Message ID: @.***>

Oxalin on Feb 23, 2024

The next version bump will include support for Windows AppX, the code has been merged and reworked.

Oxalin on Dec 12, 2023