search

glimmerjs / glimmer-experimental

A set of experimental high-level APIs built on Glimmer.js
https://glimmerjs.github.io/glimmer-experimental/
58 stars 26 forks source link

Module not found: Error: Can't resolve '@glimmer/bundle-compiler' #77

Closed rajasegar closed 3 years ago

rajasegar commented 4 years ago

Using @glimmerx/blueprint app throws errors in Ubuntu

OS version (Ubuntu 20.04 LTS)

$ uname -a
Linux inspiron 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Node version

$ node -v
v12.18.1

Yarn version

$ yarn -v
1.22.4

Console output

$ yarn start
✖ ｢wdm｣: Hash: 81ecc0f034a5da4b974f
Version: webpack 4.43.0
Time: 15998ms
Built at: 06/29/2020 5:45:37 AM
                                      Asset       Size  Chunks             Chunk Names
                              app.bundle.js   2.46 MiB     app  [emitted]  app
images/e14e33bc4ea14463b5e068ac55c6081f.svg   1.04 KiB          [emitted]  
                                 index.html  545 bytes          [emitted]  
                         public/favicon.png   2.04 KiB          [emitted]  
                         public/logo192.png   5.96 KiB          [emitted]  
                         public/logo512.png     17 KiB          [emitted]  
                       public/manifest.json  498 bytes          [emitted]  
                          public/robots.txt   51 bytes          [emitted]  
                            tests.bundle.js   2.73 MiB   tests  [emitted]  tests
                           tests/index.html  387 bytes          [emitted]  
Entrypoint app = app.bundle.js
Entrypoint tests = tests.bundle.js
 [1] multi (webpack)-dev-server/client?http://localhost:8080 ./src/index.js 40 bytes {app} [built]
[11] multi (webpack)-dev-server/client?http://localhost:8080 ./tests/rendering/App.test.js 40 bytes {tests} [built]
 [./node_modules/@glimmerx/core/dist/modules/index.js] 522 bytes {app} {tests} [built]
 [./node_modules/strip-ansi/index.js] 162 bytes {app} {tests} [built]
 [./node_modules/webpack-dev-server/client/index.js?http://localhost:8080] (webpack)-dev-server/client?http://localhost:8080 4.29 KiB {app} {tests} [built]
 [./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.51 KiB {app} {tests} [built]
 [./node_modules/webpack-dev-server/client/socket.js] (webpack)-dev-server/client/socket.js 1.53 KiB {app} {tests} [built]
 [./node_modules/webpack-dev-server/client/utils/createSocketUrl.js] (webpack)-dev-server/client/utils/createSocketUrl.js 2.91 KiB {app} {tests} [built]
 [./node_modules/webpack-dev-server/client/utils/log.js] (webpack)-dev-server/client/utils/log.js 964 bytes {app} {tests} [built]
 [./node_modules/webpack-dev-server/client/utils/reloadApp.js] (webpack)-dev-server/client/utils/reloadApp.js 1.59 KiB {app} {tests} [built]
 [./node_modules/webpack-dev-server/client/utils/sendMessage.js] (webpack)-dev-server/client/utils/sendMessage.js 402 bytes {app} {tests} [built]
 [./node_modules/webpack/hot sync ^\.\/log$] (webpack)/hot sync nonrecursive ^\.\/log$ 170 bytes {app} {tests} [built]
 [./src/App.js] 1.17 KiB {app} {tests} [built]
 [./src/index.js] 171 bytes {app} [built]
 [./tests/rendering/App.test.js] 362 bytes {tests} [built]
    + 444 hidden modules

ERROR in ./node_modules/@glimmer/opcode-compiler/dist/modules/es2017/lib/program-context.js
Module not found: Error: Can't resolve '@glimmer/bundle-compiler' in '/home/rajasegar/Public/www/hello-glimmerx/node_modules/@glimmer/opcode-compiler/dist/modules/es201
7/lib'                                                                                                                                                                 
 @ ./node_modules/@glimmer/opcode-compiler/dist/modules/es2017/lib/program-context.js 3:0-58
 @ ./node_modules/@glimmer/opcode-compiler/dist/modules/es2017/index.js
 @ ./node_modules/@glimmerx/core/dist/modules/src/renderComponent/CompileTimeResolver.js
 @ ./node_modules/@glimmerx/core/dist/modules/index.js
 @ ./src/index.js

ERROR in ./node_modules/@glimmerx/component/dist/modules/src/GlimmerComponentManager.js
Module not found: Error: Can't resolve '@glimmerx/service' in '/home/rajasegar/Public/www/hello-glimmerx/node_modules/@glimmerx/component/dist/modules/src'
 @ ./node_modules/@glimmerx/component/dist/modules/src/GlimmerComponentManager.js 3:0-76 25:38-64 28:6-17
 @ ./node_modules/@glimmerx/component/dist/modules/src/Component.js
 @ ./node_modules/@glimmerx/component/dist/modules/index.js
 @ ./src/App.js
 @ ./src/index.js

ERROR in ./node_modules/@glimmerx/core/dist/modules/src/renderComponent/index.js
Module not found: Error: Can't resolve '@glimmerx/service' in '/home/rajasegar/Public/www/hello-glimmerx/node_modules/@glimmerx/core/dist/modules/src/renderComponent'
 @ ./node_modules/@glimmerx/core/dist/modules/src/renderComponent/index.js 8:0-63 97:7-33
 @ ./node_modules/@glimmerx/core/dist/modules/index.js
 @ ./src/index.js
Child HtmlWebpackCompiler:
     2 assets
    Entrypoint HtmlWebpackPlugin_0 = __child-HtmlWebpackPlugin_0
    Entrypoint HtmlWebpackPlugin_1 = __child-HtmlWebpackPlugin_1
    [./node_modules/html-webpack-plugin/lib/loader.js!./index.html] 772 bytes {HtmlWebpackPlugin_0} [built]
    [./node_modules/html-webpack-plugin/lib/loader.js!./tests/index.html] 609 bytes {HtmlWebpackPlugin_1} [built]
(node:5630) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, stat '/initrd.img'
(node:5630) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, o
r by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=str
ict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)                                                                            
(node:5630) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js
 process with a non-zero exit code.                                                                                                                                    
(node:5630) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, stat '/initrd.img.old'
(node:5630) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, o
r by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=str
ict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)                                                                            
(node:5630) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, stat '/vmlinuz'
(node:5630) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, o
r by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=str
ict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)                                                                            
(node:5630) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, stat '/vmlinuz.old'
(node:5630) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, o
r by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=str
ict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
mike-north commented 3 years ago

FYI I ran into this problem, but following the instructions in the README (particularly the installation of other packages) resolved it for me.

acorncom commented 3 years ago

I setup a test app without issue as well, @rajasegar is this still a problem for you or can we close this issue?

rajasegar commented 3 years ago

I have not checked it later, you can close this issue, will open a new one if I have any new issue

rajasegar commented 3 years ago

Closing this issue, since it's working as expected