remix-pwa: Not able to install

Issue

Ran following: yarn add esbuild yarn add remix-pwa

(also tried npm for both after running into this issue. Same issues`

Output:

error app/node_modules/remix-pwa: Command failed.
Exit code: 1
Command: npm run start
Arguments: 
Directory: app/node_modules/remix-pwa
Output:
> remix-pwa@0.3.4 start
> node --loader ts-node/esm .\cli.ts

(node:7497) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
app/node_modules/ts-node/dist-raw/node-esm-resolve-implementation.js:383
    throw new ERR_MODULE_NOT_FOUND(
          ^
CustomError: Cannot find module 'app/node_modules/remix-pwa/.cli.ts' imported from app/node_modules/remix-pwa/
    at finalizeResolution (app/node_modules/ts-node/dist-raw/node-esm-resolve-implementation.js:383:11)
    at moduleResolve (app/node_modules/ts-node/dist-raw/node-esm-resolve-implementation.js:818:10)
    at Object.defaultResolve (app/node_modules/ts-node/dist-raw/node-esm-resolve-implementation.js:929:11)
    at resolve (app/node_modules/ts-node/src/esm.ts:163:38)
    at ESMLoader.resolve (node:internal/modules/esm/loader:530:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:251:18)
    at ESMLoader.import (node:internal/modules/esm/loader:332:22)
    at node:internal/modules/run_main:54:28
    at loadESM (node:internal/process/esm_loader:88:11)
    at async handleMainPromise (node:internal/modules/run_main:61:12)
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 44 (27 by maintainers)

Most upvoted comments

With regards to the root, I would try to reduce syntax errors, it should be an easy fix.

That’s the strange thing, in the original root.tsx there is no syntax error. And also with the applied changes (let location …) as seen in the screenshot, this still shouldn’t be a syntax error. But I can easily fix this for me by removing the line temporarely.

Sadly also no success with node v14.16.1 and @0.6.2 or @0.6.3