loynoir

loynoir

Member Since 1 year ago

Experience Points
0
follower
Lessons Completed
0
follow
Best Reply Awards
61
repos

289 contributions in the last year

Pinned
⚡ work and tested example jest config if you have ESM only dependency
⚡ Python Fire is a library for automatically generating command line interfaces (CLIs) from absolutely any Python object.
⚡ SSDB - A fast NoSQL database, an alternative to Redis
⚡ python os.path.expanduser equivalent in nodejs
⚡ python os.path.expanduser equivalent in golang
⚡ golang defer equivalent in python
Activity
May
16
2 days ago
Activity icon
issue

loynoir issue comment yarnpkg/berry

loynoir
loynoir

[Bug?]: repo's package.json should be updated AFTER dependency postinstall script

Self-service

  • I'd be willing to implement a fix

Describe the bug

Actually, yarn berry update repo's package.json BEFORE dependency preinstall script.

Causing different behavior compared to both npm and pnpm when running script

  • preinstall
  • install
  • postinstall

To reproduce

Reproduce

Given

  • repo has
{
  "devDependencies": {
    "foo": "1.0.22"
  }
}
  • foo has script preinstall, install, postinstall, to detect update from which version
# update from
jq \
    ".devDependencies[\"${name}\"]" \
    "${INIT_CWD}"/package.json
# update to
echo "${npm_package_version}"
  • update foo from 1.0.22 to 1.0.23
{{PM}} {{ADD}} -D [email protected]

Actual

yarn berry output

"1.0.23"
1.0.23
"1.0.23"
1.0.23
"1.0.23"
1.0.23

Expected

npm output

"^1.0.22"
1.0.23
"^1.0.22"
1.0.23
"^1.0.22"
1.0.23

pnpm output

"1.0.22"
1.0.23
"1.0.22"
1.0.23
"1.0.22"
1.0.23

Environment

Node: 16.14.2

Yarn: 3.2.0

Additional context

No response

loynoir
loynoir

@merceyz OK, forget about preinstall and install.

npm postinstall output

"^1.0.22"
1.0.23

pnpm postinstall output

"^1.0.22"
1.0.23

yarnBerry postinstall output

"1.0.23"
1.0.23

Both npm and pnpm update package.json version after postinstall. But yarnBerry update package.json version before postinstall, which makes a update function useless.

function update(fromVer, toVer) {
  // babel transform `fromVer` to `toVer`
}

Activity icon
issue

loynoir issue yarnpkg/berry

loynoir
loynoir

[Bug?]: repo's package.json should be updated AFTER dependency postinstall script

Self-service

  • I'd be willing to implement a fix

Describe the bug

Actually, yarn berry update repo's package.json BEFORE dependency preinstall script.

Causing different behavior compared to both npm and pnpm when running script

  • preinstall
  • install
  • postinstall

To reproduce

Reproduce

Given

  • repo has
{
  "devDependencies": {
    "foo": "1.0.22"
  }
}
  • foo has script preinstall, install, postinstall, to detect update from which version
# update from
jq \
    ".devDependencies[\"${name}\"]" \
    "${INIT_CWD}"/package.json
# update to
echo "${npm_package_version}"
  • update foo from 1.0.22 to 1.0.23

Actual

yarn berry output

"1.0.23"
1.0.23
"1.0.23"
1.0.23
"1.0.23"
1.0.23

Expected

npm output

"^1.0.22"
1.0.23
"^1.0.22"
1.0.23
"^1.0.22"
1.0.23

pnpm output

"1.0.22"
1.0.23
"1.0.22"
1.0.23
"1.0.22"
1.0.23

Environment

Node: 16.14.2

Yarn: 3.2.0

Additional context

No response

May
14
4 days ago
Activity icon
issue

loynoir issue comment yarnpkg/berry

loynoir
loynoir

[Bug?]: install is not really offline

Self-service

  • I'd be willing to implement a fix

Describe the bug

With re-usable global cache enabled, can not perform a offline install.

To reproduce

Given

  • no server listening on port 1234
  • install same dependencies before reproduce using global cache

Reproduce

$ env \
  YARN_ENABLE_GLOBAL_CACHE=true \
  YARN_NPM_REGISTRY_SERVER=http://127.0.0.1:1234 \
  yarn

Expect

no error

Actual

➤ YN0001: │ RequestError: connect ECONNREFUSED 127.0.0.1:1234

Environment

Node: 16.14.2

Yarn: 3.2.0

Additional context

No response

loynoir
loynoir

@arcanis Isn't unreachable enought? 😅

$ env \
  YARN_ENABLE_GLOBAL_CACHE=true \
  YARN_NPM_REGISTRY_SERVER=https://unreachable \
  yarn

Anyway, full reproduction

  • online pnpm install: OK
  • offline pnpm install: OK
  • online yarn berry bootstrap: OK
  • online yarn berry install: OK
  • offline yarn berry bootstrap: FAIL
  • offline yarn berry install: FAIL

https://github.com/loynoir/reproduce-yarnBerry-4455

Activity icon
issue

loynoir issue yarnpkg/berry

loynoir
loynoir

[Bug?]: not really offline

Self-service

  • I'd be willing to implement a fix

Describe the bug

With re-usable global cache enabled, can not perform a offline install.

To reproduce

Given

  • no server listening on port 1234
  • install same dependencies before reproduce using global cache

Reproduce

$ env \
  YARN_ENABLE_GLOBAL_CACHE=true \
  YARN_NPM_REGISTRY_SERVER=http://127.0.0.1:1234 \
  yarn

Expect

no error

Actual

➤ YN0001: │ RequestError: connect ECONNREFUSED 127.0.0.1:1234

Environment

Node: 16.14.2

Yarn: 3.2.0

Additional context

No response

Activity icon
issue

loynoir issue sindresorhus/type-fest

loynoir
loynoir

`PackageJson` should be sub type of `JsonValue`

import type { JsonValue, PackageJson } from "type-fest"

function fn(j: JsonValue) {
  console.log(j)
}

const pj: PackageJson = {}
fn(pj)

Expect

$ ts --noEmit
# (no error)

Actual

$ ts --noEmit
src/index.ts(8,4): error TS2345: Argument of type 'PackageJson' is not assignable to parameter of type 'JsonValue'.
  Type 'PackageJson' is not assignable to type 'JsonObject'.
    Index signature for type 'string' is missing in type 'PackageJson'.
May
13
5 days ago
Activity icon
issue

loynoir issue prettier/prettier

loynoir
loynoir

[feat] prefer shorthand properties

Prettier 2.6.2 Playground link

# Options (if any):

Input:

var o = { a: a, b: b, c: c };
export { foo as foo }

Output:

var o = { a: a, b: b, c: c };
export { foo as foo }

Expected behavior:

var o = { a, b, c };
export { foo }

Situation

Given

  • { X }

When

  • <F2> twice to rename reference

Becomes

  • { Y: Y } or { Y as Y }.

Why

Would be nice if prettier can make them shorthand again, as short-handify after rename-reference is not part of language server protocol.

Related Doc

https://babeljs.io/docs/en/babel-plugin-transform-shorthand-properties

May
11
1 week ago
Activity icon
issue

loynoir issue comment esm-dev/esm.sh

loynoir
loynoir

[feat] http only

What

https://github.com/esm-dev/esm.sh/blob/46940b3b72de52cb2259d8973c9f959481e68dc4/server/embed/index.html#L41

Currently, a http only server is not working, unless hostname is hardcoded localhost.

Feature Request

https://github.com/esm-dev/esm.sh/blob/46940b3b72de52cb2259d8973c9f959481e68dc4/server/embed/index.html#L26

Add a place holder to allow customize http only hostname

loynoir
loynoir

are you saying something like --http-only-hostname=localhost

Ah, yes 😃

Activity icon
issue

loynoir issue comment esm-dev/esm.sh

loynoir
loynoir

Fix using `arguments` in arrow function

loynoir
loynoir

@ije Maybe consider using someeslint rules, prevent some future mistaks?

Activity icon
issue

loynoir issue comment eslint/eslint

loynoir
loynoir

Support having plugins as dependencies in shareable config

My shareable config uses rules from an external plugin and I would like to make it a dependency so the user doesn't have to manually install the plugin manually. I couldn't find any docs on this, but it doesn't seem to work, so I'll assume it's not currently supported.

module.js:338
    throw err;
          ^
Error: Cannot find module 'eslint-plugin-no-use-extend-native'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at /usr/local/lib/node_modules/eslint/lib/cli-engine.js:106:26
    at Array.forEach (native)
    at loadPlugins (/usr/local/lib/node_modules/eslint/lib/cli-engine.js:97:21)
    at processText (/usr/local/lib/node_modules/eslint/lib/cli-engine.js:182:5)
    at processFile (/usr/local/lib/node_modules/eslint/lib/cli-engine.js:224:12)
    at /usr/local/lib/node_modules/eslint/lib/cli-engine.js:391:26

I assume it's because you only try to load the plugin when the config is finished merging.

Other shareable configs that depend on a plugin instructs the users to manually install the plugin too and they have it in peerDependencies. I find this sub-optimal though and I don't want the users to have to care what plugins my config uses internally.

The whole point of shareable configs is to minimize boilerplate and overhead, so this would be a welcome improvement.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

loynoir
loynoir

Was using pnpm, this was never a problem with public-hoist-pattern[]=*eslint*.

But, recently I try yarn berry.

Does any one know what's the workaround for yarn berry, the hoist way, or any way to let yarn berry auto install peer dependency?

Activity icon
issue

loynoir issue esm-dev/esm.sh

loynoir
loynoir

wrong node_process polyfill

Actual

https://github.com/esm-dev/esm.sh/blob/46940b3b72de52cb2259d8973c9f959481e68dc4/server/embed/polyfills/node_process.js#L234-L235

Arrow function don't have arguments

(()=>{arguments})()
Uncaught ReferenceError: arguments is not defined

Expected

(function(){arguments})()

OK

Fix

https://github.com/esm-dev/esm.sh/pull/322

Activity icon
issue

loynoir issue esm-dev/esm.sh

loynoir
loynoir

[feat] http only

What

https://github.com/esm-dev/esm.sh/blob/46940b3b72de52cb2259d8973c9f959481e68dc4/server/embed/index.html#L41

Currently, a http only server is not working, unless hostname is hardcoded localhost.

Feature Request

https://github.com/esm-dev/esm.sh/blob/46940b3b72de52cb2259d8973c9f959481e68dc4/server/embed/index.html#L26

Add a place holder to allow customize http only hostname

pull request

loynoir pull request esm-dev/esm.sh

loynoir
loynoir

Fix using `arguments` in arrow function

Activity icon
created branch

loynoir in loynoir/esm.sh create branch feat-http-only

createdAt 1 week ago
Activity icon
created branch

loynoir in loynoir/esm.sh create branch fix-arrow-fn-arguments

createdAt 1 week ago
Activity icon
fork

loynoir forked esm-dev/esm.sh

⚡ A fast, global content delivery network for ES Modules.
loynoir MIT License Updated
fork time in 1 week ago
May
10
1 week ago
Activity icon
issue

loynoir issue wclr/yalc

loynoir
loynoir

[feat] path name with version

Current

{
    "devDependencies": {
        "@foo/bar": "file:.yalc/@foo/bar",
        "a": "1.2.3",
        "b": "1.2.3"
    }
}

Expected, with version, more symmetric, and seems more reproducible

{
    "devDependencies": {
        "@foo/bar": "file:.yalc/@foo/[email protected]",
        "a": "1.2.3",
        "b": "1.2.3"
    }
}
Apr
23
3 weeks ago
Activity icon
issue

loynoir issue yarnpkg/berry

loynoir
loynoir

[Feature] docs on equivalent operations compared to other PM

  • I'd be willing to implement this feature (contributing guide)
  • This feature is important to have in this repository; a contrib plugin wouldn't do

Describe the user story Was not a yarn berry user.

Try a pnpm repo on a remote machine.

Try bi-sync way first, but give up as it's sync is not blocking.

Then the fuse way, but the large node_modules get things very very slow.

For example

  1. sshfs + pnpm, need 15min to do a require('benny')
  2. nfs + pnpm, need 10min.

Then I remember yarn berry, awesome!

  1. sshfs + yarn berry, 1min
  2. nfs + yarn berry, 3 seconds

So, decided to use yarn berry in some situations.

But, I gonna ask some things, seems but found in document.

I use typescript, and ESM. Using other PM, I can run .mts by

$ node --loader esbuild-node-loader ./foobar.mts

How can I do that if i use yarn berry?

  1. Without node_modules, what can I do if I want to quick modify source of a dependency?

Describe the solution you'd like

Describe the drawbacks of your solution

Describe alternatives you've considered

Activity icon
issue

loynoir issue comment pnpm/pnpm

loynoir
loynoir

Pnpm publish doesn't work correctly with workspaces and npm 8.5.0

(I'm not sure if this issue is related to pnpm or npm)

pnpm version:

6.31.0

Code to reproduce the issue:

  1. Install the latest version of NPM (8.5.0)
  2. Create a project with workspaces, setup changesets and add dependencies from one workspace to another with something like "foo": "workspace:*"
  3. Run all the steps to create a new changeset and run pnpm publish -r

Expected behavior:

Workspace references have been replaced with an actual version in the published package.

Actual behavior:

The published package still contains "workspace:*" as version, making it not installable.

Additional information:

  • When I do a manual pnpm pack the version is being applied
  • Downgrading NPM to version 8.4.1 solves the issue
loynoir
loynoir

https://github.com/pnpm/pnpm/issues/4438

i used workaround, add .files field to package.json

Apr
22
3 weeks ago
Activity icon
issue

loynoir issue comment esm-dev/esm.sh

loynoir
loynoir

Make esm.sh into a library

Hello @ije, been a little while. I'm getting back into this project a little more, and realizing that it would be a lot easier to make it work for use cases that I'm trying to, if the core functionality was a library that you can pass objects to rather than a server with configuration options.

That would keep the implementations and drivers light in the library, and open free server version of the project.

What do you think?

How would it help me and where is this coming from? The more I get into the AWS linkage, the more I think a library would feel better in this separation of concerns.

loynoir
loynoir

Hi, guys. How can you install esm.sh binary?

My not freq used esm.sh docker image now takes 1.5G.

Apr
21
3 weeks ago
Activity icon
issue

loynoir issue egoist/tsup

loynoir
loynoir

`.mts` support

index.mts

const answer: number = 42
export { answer }
$ tsup index.mts
Unexpected token (Note that you need plugins to import files that are not JavaScript)
1: const answer: number = 42
               ^
2: export { answer }
Activity icon
issue

loynoir issue comment node-fetch/node-fetch

loynoir
loynoir

chore(cjs/esm): Bundle module and use package exports

THIS IS A PROPOSAL

As explained in #1226, the fact that node-fetch v3.0.0-beta.10 is now pure ESM cause multiple problems with existing codebases.

In JavaScript codebases, we need to use the async import() which can create a lot of changes. In TypeScript codebases (with cjs module mode), it is impossible to use node-fetch anymore.

I think that ESM is the future but it is not as stable as we think and it is not ready to be used everywhere. The best way to ensure that all existing codebases can migrate to v3 is to provide both cjs and esm versions of this module.

For this, I introduced esbuild which can transpile ESM to CJS and also can bundle the package.

You can say: "node does not need packages to be bundled", which is true. However, bundling is a good practice to reduce the module loading time, disk operations, memory footprint, etc. It can also be used to bundle internal dependencies and so reduce the npm dependency tree (reduce install time, disk operations, memory footprint, npm hell, etc.).

What is the purpose of this pull request?

  • Documentation update
  • Bug fix
  • New feature
  • Other, please explain:
    • allow both esm and cjs exports
    • reduce module loading time
    • reduce disk operations
    • reduce module memory footprint

What changes did you make? (provide an overview)

  • use esbuild to bundle module in esm and cjs format
  • bundle dependencies to reduce module size
  • use package exports to automatically select the appropriate version
  • add build step to prepublishOnly
  • add build step to ci

Which issue (if any) does this pull request address?

#1226 #1217

Is there anything you'd like reviewers to know?

In this implementation, I bundle both data-uri-to-buffer and fetch-blob into the final result allowing us to be dependency free.

I think data-uri-to-buffer is safe to bundle because it's an internal dependency. However, I think fetch-blob should not be bundled because it could be used by the consumer.

What do you think?

Note 1: If we do not want to bundle fetch-blob, we have to provide a CJS export for it. Note 2: If we do not bundle fetch-blob, the install size will be very large as mentioned by @akaupi in #1217. Maybe we could make fetch-blob dependency free by using esbuild to bundle web-streams-polyfill .

loynoir
loynoir

https://nodejs.org/en/blog/announcements/v18-release-announce/#fetch-experimental

In Node.js 18, an experimental global fetch API is available by default.

$ node
Welcome to Node.js v18.0.0.
> fetch
[AsyncFunction: fetch]
Activity icon
issue

loynoir issue egoist/tsup

loynoir
loynoir

Question: How to keep `class X {}`, avoid `var X = class {}`?

Input

class Foo {}
export { Foo }

Output

var Foo = class {
};
export {
  Foo
};
Activity icon
issue

loynoir issue comment patriksimek/vm2

loynoir
loynoir

VMError: Unexpected access to key 'Symbol(nodejs.util.inspect.custom)'

Error from '3.9.6' to '3.9.9'.

Last ok version is '3.9.5'

loynoir
loynoir
  • vm2 newbee on day1
  • spawn a node 16 repl and run the example "What is the difference between Node's vm and vm2?"

nodejs repl, vm2 3.9.5

> const {VM} = require('vm2');
> new VM().run('this.constructor.constructor("return process")().exit()');
> // OK

nodejs repl, vm2 3.9.9

> const {VM} = require('vm2');
> new VM().run('this.constructor.constructor("return process")().exit()');
Uncaught VMError: Unexpected access to key 'Symbol(nodejs.util.inspect.custom)'
Activity icon
issue

loynoir issue patriksimek/vm2

loynoir
loynoir

VMError: Unexpected access to key 'Symbol(nodejs.util.inspect.custom)'

Error from '3.9.6' to '3.9.9'.

Last ok version is '3.9.5'

Apr
19
4 weeks ago
Activity icon
issue

loynoir issue esm-dev/esm.sh

loynoir
loynoir

`go install` error

As comparison, go install esbuild is ok

$ go install github.com/evanw/esbuild/cmd/[email protected] && echo OK
OK
$ go install github.com/esm-dev/[email protected]
go: downloading github.com/esm-dev/esm.sh v0.1.0
go: github.com/esm-dev/[email protected]: github.com/esm-dev/[email protected]: parsing go.mod:
        module declares its path as: esm.sh
                but was required as: github.com/esm-dev/esm.sh
$ go install [email protected]
go: [email protected]: unrecognized import path "esm.sh": parse https://esm.sh/?go-get=1: no go-import meta tags ()

Maybe change module name esm.sh to github.com/esm-dev/esm.sh?

Apr
17
1 month ago
Activity icon
issue

loynoir issue comment hashicorp/vagrant

loynoir
loynoir

`vagrant up` fail when virtualbox networking mode "Not attached"

Keyword

  • vagrant up
  • ssh
  • virtualbox networking mode: "Not attached"
  • serial console

Usage

Cut networking access from a vm.

https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/networkingmodes.html

Control it by

  • Set up guest's grub with serial console config
  • Set up host's minicom config

Then vagrant up fail, as it try to ssh into guest, which have been cut network access.

Vagrant version

Vagrant 2.2.19

Host operating system

ArchLinux

Guest operating system

hashicorp/bionic64

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "hashicorp/bionic64"
  config.vm.provider "virtualbox" do |v|
    # offline mode
    v.customize ["modifyvm", :id, "--nic1", "none"]

    # serial port
    v.customize ["modifyvm", :id, "--uart1", "0x3f8", "4"]
    v.customize ["modifyvm", :id, "--uartmode1", "server", "/tmp/vmserial"]
  end

  # config serial console inside guest
  config.vm.provision "shell", inline: $config_grub_serial_console
end

Debug output

$ vagrant up && minicom
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'hashicorp/bionic64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/bionic64' version '1.0.282' is up to date...
==> default: Setting the name of the VM: xxx
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH xxx
    default: SSH xxx
    default: SSH xxx
    default: Warning: Connection refused. Retrying...
    default: Warning: Connection refused. Retrying...
    (~30 times)
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

Expected behavior

vagrant up OK.

Actual behavior

vagrant up FAIL.

Steps to reproduce

  1. vagrant up FAIL
  2. minicom OK

References

loynoir
loynoir

Some solve ideas

  • how to disable ssh, to prevent vagrant up fail, when guest not attach network
  • how to integrate serial console with vagrant
  • how to let vagrant ssh over serial port 😃
Activity icon
issue

loynoir issue hashicorp/vagrant

loynoir
loynoir

`vagrant up` hangs because `ssh` to running vm cut network access

Keyword

  • vagrant up
  • ssh
  • virtualbox networking mode: "Not attached"
  • serial console

Usage

Cut networking access from a vm.

https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/networkingmodes.html

Control it by

  • Set up guest's grub with serial console config
  • Set up host's minicom config

Then vagrant up fail, as it try to ssh into guest, which have been cut network access.

Vagrant version

Vagrant 2.2.19

Host operating system

ArchLinux

Guest operating system

hashicorp/bionic64

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "hashicorp/bionic64"
  config.vm.provider "virtualbox" do |v|
    # offline mode
    v.customize ["modifyvm", :id, "--nic1", "none"]

    # serial port
    v.customize ["modifyvm", :id, "--uart1", "0x3f8", "4"]
    v.customize ["modifyvm", :id, "--uartmode1", "server", "/tmp/vmserial"]
  end

  # config serial console inside guest
  config.vm.provision "shell", inline: $config_grub_serial_console
end

Debug output

$ vagrant up && minicom
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'hashicorp/bionic64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/bionic64' version '1.0.282' is up to date...
==> default: Setting the name of the VM: xxx
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH xxx
    default: SSH xxx
    default: SSH xxx
    default: Warning: Connection refused. Retrying...
    default: Warning: Connection refused. Retrying...
    (~30 times)
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

Expected behavior

vagrant up OK.

Actual behavior

vagrant up FAIL.

Steps to reproduce

  1. vagrant up FAIL
  2. minicom OK

References

Apr
16
1 month ago
Activity icon
issue

loynoir issue hashicorp/vagrant

loynoir
loynoir

[docs] code intelligence

Is your feature request related to a problem? Please describe. Sorry, I know nothing about ruby language.

But, I guess code intelligence exists in ruby ecosystem.

And vagrantfile is written in ruby.

But I installed several vscode extensions, and see no code intelligence.

Is there code intelligence vscode solutions for ruby, or more specifically said vagrantfile?

Expected

  1. hover on config.vm.disk

show docs, need export VAGRANT_EXPERIMENTAL="disks"

  1. tab after config.vm.disk
config.vm.disk :disk, disk_ext: disk_ext, file: file, name: name, primary: primary, size: size

Actual

  1. hover on config.vm.disk

show nothing

  1. tab after config.vm.disk

show nothing

Describe the solution you'd like

Describe alternatives you've considered

Additional context Archlinux user. Install vagrant from package manager.

Activity icon
issue

loynoir issue hashicorp/vagrant

loynoir
loynoir

[feat] custom ssh command, eg: `autossh`

Is your feature request related to a problem? Please describe. vagrant ssh, then reboot

Expected: Able to auto reconnect

Current: Connection to xxx closed by remote host

Describe the solution you'd like

config.ssh.custom_ssh = "autossh -M 0"

Describe alternatives you've considered

Additional context

Previous