Razzle and yarn long startup time

[icyrockcom]

Trying to use razzle (3.3.11) with yarn (2.4.0)

$ yarn --version
2.4.0
$ yarn dlx razzle -v
➤ YN0000: ┌ Resolution step
➤ YN0061: │ mkdirp@npm:0.5.3 is deprecated: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
➤ YN0061: │ chokidar@npm:2.1.8 is deprecated: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
➤ YN0061: │ fsevents@npm:1.2.13 is deprecated: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
➤ YN0061: │ fsevents@npm:1.2.13 is deprecated: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
➤ YN0061: │ urix@npm:0.1.0 is deprecated: Please see https://github.com/lydell/urix#deprecated
➤ YN0061: │ resolve-url@npm:0.2.1 is deprecated: https://github.com/lydell/resolve-url#deprecated
➤ YN0032: │ nan@npm:2.14.2: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ request@npm:2.88.2 is deprecated: request has been deprecated, see https://github.com/request/request/issues/3142
➤ YN0032: │ fsevents@npm:2.3.1: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ fsevents@npm:2.3.1: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ har-validator@npm:5.1.5 is deprecated: this library is no longer supported
➤ YN0061: │ left-pad@npm:1.3.0 is deprecated: use String.prototype.padStart()
➤ YN0061: │ request-promise-native@npm:1.0.9 is deprecated: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
➤ YN0032: │ evp_bytestokey@npm:1.0.3: Implicit dependencies on node-gyp are discouraged
➤ YN0002: │ razzle-dev-utils@npm:3.3.11 doesn't provide webpack (p2e3ef), requested by webpack-dev-server
➤ YN0002: │ react-dev-utils@npm:10.2.0 doesn't provide typescript (pd22b6), requested by fork-ts-checker-webpack-plugin
➤ YN0002: │ react-dev-utils@npm:10.2.0 doesn't provide webpack (p59db9), requested by fork-ts-checker-webpack-plugin
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 5s 430ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 389ms
➤ YN0000: ┌ Link step
➤ YN0062: │ fsevents@patch:fsevents@npm%3A1.2.13#builtin<compat/fsevents>::version=1.2.13&hash=11e9ea The platform linux is incompatible with this module, build skipped.
➤ YN0000: └ Completed in 1s 707ms
➤ YN0000: Done with warnings in 7s 767ms

razzle, 3.3.11

Is it expected for it to take 7+s to start up / any ideas how to speed this up?

[merceyz]

Read the documentation for dlx https://yarnpkg.com/cli/dlx, you're basically running yarn add razzle && yarn razzle --version && yarn remove razzle, what you're probably after is to just run yarn razzle --version in your current project https://yarnpkg.com/cli/run

[icyrockcom]

@merceyz Got it, that makes sense then. yarn razzle --version works fine, but yarn run start with this:

{
...
  "scripts": {
    "start": "razzle start",
  }
...
}

fails results in:

permission denied: razzle

[merceyz]

I'm guessing some sort of anti-virus is blocking it, should be fixed in latest master, you can confirm with yarn set version from sources

[icyrockcom]

Thanks @merceyz. I'm on Xubuntu which has /tmp mounted as noexec and looks like yarn is trying to run executables from there, so it fails. Was there ever an issue like that before?

[arcanis]

Nope, that's the first report. You probably can workaround it by setting TMPDIR to another location on your disk (I'm not certain we can/should really do anything about it, since it works everywhere else 🤔).

[icyrockcom]

Thanks @arcanis Yeah, makes sense. Interesting that this is the first report since I see a lot of reports (even on non-Ubuntu, e.g. RHEL 7, CentOS 7) where /tmp is noexec.