[GH-ISSUE #327] Build failed

kerem commented

2026-03-16 13:32:32 +03:00

Owner

Originally created by @pierol on GitHub (Nov 22, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/327

Originally assigned to: @liyasthomas on GitHub.

Describe the bug
Trying to build the package on Windows 10 machine with

npm run build

WARNING in ./node_modules/yargs-parser/index.js 539:21-48
Critical dependency: the request of a dependency is an expression
 @ ./assets/js/curlparser.js
 @ ./node_modules/babel-loader/lib??ref--2-0!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=js&
 @ ./pages/index.vue?vue&type=script&lang=js&
 @ ./pages/index.vue
 @ ./.nuxt/router.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

ERROR in ./layouts/default.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib??ref--2-0!./node_modules/vue-loader/lib??vue-loader-options!./layouts/default.vue?vue&type=script&lang=js&)
Module not found: Error: Can't resolve '../.postwoman/version.json' in 'R:\Sites\opensource\postwoman-master\layouts'
 @ ./layouts/default.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib??ref--2-0!./node_modules/vue-loader/lib??vue-loader-options!./layouts/default.vue?vue&type=script&lang=js&) 284:0-54 316:19-34
 @ ./layouts/default.vue?vue&type=script&lang=js&
 @ ./layouts/default.vue
 @ ./.nuxt/App.js
 @ ./.nuxt/index.js
 @ ./.nuxt/client.js
 @ multi ./.nuxt/client.js

 FATAL  Nuxt build error                                                                                      22:29:04

  at WebpackBundler.webpackCompile (node_modules\@nuxt\webpack\dist\webpack.js:5314:21)
  at processTicksAndRejections (internal/process/task_queues.js:93:5)
  at async WebpackBundler.build (node_modules\@nuxt\webpack\dist\webpack.js:5263:5)
  at async Builder.build (node_modules\@nuxt\builder\dist\builder.js:5597:5)
  at async Generator.initiate (node_modules\@nuxt\generator\dist\generator.js:70:7)
  at async Generator.generate (node_modules\@nuxt\generator\dist\generator.js:40:5)
  at async Object.run (node_modules\@nuxt\cli\dist\cli-build.js:96:7)
  at async NuxtCommand.run (node_modules\@nuxt\cli\dist\cli-command.js:2575:7)


   ╭─────────────────────────────╮
   │                             │
   │   ✖ Nuxt Fatal Error        │
   │                             │
   │   Error: Nuxt build error   │
   │                             │
   ╰─────────────────────────────╯

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! postwoman@1.0.0 build: `nuxt build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the postwoman@1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\piero\AppData\Roaming\npm-cache\_logs\2019-11-22T21_29_04_067Z-debug.log

To Reproduce

Steps to reproduce the behavior (npm version 6.12.0, node version 12.13.0, SO Windows 10 1909):

Download the ZIP and unzip it
from inside the project folder run npm install
npm run build
See error

Originally created by @pierol on GitHub (Nov 22, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/327 Originally assigned to: @liyasthomas on GitHub. **Describe the bug** Trying to build the package on Windows 10 machine with `npm run build` ```dos WARNING in ./node_modules/yargs-parser/index.js 539:21-48 Critical dependency: the request of a dependency is an expression @ ./assets/js/curlparser.js @ ./node_modules/babel-loader/lib??ref--2-0!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=js& @ ./pages/index.vue?vue&type=script&lang=js& @ ./pages/index.vue @ ./.nuxt/router.js @ ./.nuxt/index.js @ ./.nuxt/client.js @ multi ./.nuxt/client.js ERROR in ./layouts/default.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib??ref--2-0!./node_modules/vue-loader/lib??vue-loader-options!./layouts/default.vue?vue&type=script&lang=js&) Module not found: Error: Can't resolve '../.postwoman/version.json' in 'R:\Sites\opensource\postwoman-master\layouts' @ ./layouts/default.vue?vue&type=script&lang=js& (./node_modules/babel-loader/lib??ref--2-0!./node_modules/vue-loader/lib??vue-loader-options!./layouts/default.vue?vue&type=script&lang=js&) 284:0-54 316:19-34 @ ./layouts/default.vue?vue&type=script&lang=js& @ ./layouts/default.vue @ ./.nuxt/App.js @ ./.nuxt/index.js @ ./.nuxt/client.js @ multi ./.nuxt/client.js FATAL Nuxt build error 22:29:04 at WebpackBundler.webpackCompile (node_modules\@nuxt\webpack\dist\webpack.js:5314:21) at processTicksAndRejections (internal/process/task_queues.js:93:5) at async WebpackBundler.build (node_modules\@nuxt\webpack\dist\webpack.js:5263:5) at async Builder.build (node_modules\@nuxt\builder\dist\builder.js:5597:5) at async Generator.initiate (node_modules\@nuxt\generator\dist\generator.js:70:7) at async Generator.generate (node_modules\@nuxt\generator\dist\generator.js:40:5) at async Object.run (node_modules\@nuxt\cli\dist\cli-build.js:96:7) at async NuxtCommand.run (node_modules\@nuxt\cli\dist\cli-command.js:2575:7) ╭─────────────────────────────╮ │ │ │ ✖ Nuxt Fatal Error │ │ │ │ Error: Nuxt build error │ │ │ ╰─────────────────────────────╯ npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! postwoman@1.0.0 build: `nuxt build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the postwoman@1.0.0 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\piero\AppData\Roaming\npm-cache\_logs\2019-11-22T21_29_04_067Z-debug.log ``` **To Reproduce** Steps to reproduce the behavior (npm version 6.12.0, node version 12.13.0, SO Windows 10 1909): 1. Download the ZIP and unzip it 2. from inside the project folder run `npm install` 3. `npm run build` 4. See error

kerem

2026-03-16 13:32:32 +03:00

closed this issue
added the
bug

need information
labels

kerem commented

2026-03-16 13:32:48 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 22, 2019):

Oh! That seems critical then. Let us investigate what went wrong and get back to you ASAP.
Thanks for reporting.

@liyasthomas commented on GitHub (Nov 22, 2019): Oh! That seems critical then. Let us investigate what went wrong and get back to you ASAP. Thanks for reporting.

kerem commented

2026-03-16 13:32:53 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 23, 2019):

I just built the project on Windows platform and everything seems to be working 😕

Make sure you build the master branch.

@liyasthomas commented on GitHub (Nov 23, 2019): I just built the project on Windows platform and everything seems to be working 😕 ![Capture](https://user-images.githubusercontent.com/10395817/69471940-a4f07b80-0dca-11ea-83f6-48b37f3547aa.PNG) Make sure you build the master branch.

kerem commented

2026-03-16 13:32:59 +03:00

Author

Owner

@pierol commented on GitHub (Nov 23, 2019):

I tried with a fresh install but the problem persist

@pierol commented on GitHub (Nov 23, 2019): I tried with a fresh install but the problem persist ![Untitled](https://user-images.githubusercontent.com/433875/69476721-d757a400-0ddd-11ea-8a7c-a4ec023343cb.jpg) ![Untitled](https://user-images.githubusercontent.com/433875/69476743-256ca780-0dde-11ea-9c82-999fb04c4e94.jpg)

kerem commented

2026-03-16 13:33:04 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 23, 2019):

Can you do a npm run dev and let me know.

@liyasthomas commented on GitHub (Nov 23, 2019): Can you do a `npm run dev` and let me know.

kerem commented

2026-03-16 13:33:09 +03:00

Author

Owner

@pierol commented on GitHub (Nov 23, 2019):

@pierol commented on GitHub (Nov 23, 2019): ![Untitled](https://user-images.githubusercontent.com/433875/69476782-af1c7500-0dde-11ea-811e-872bb54fca86.jpg) ![Untitled-02](https://user-images.githubusercontent.com/433875/69476783-afb50b80-0dde-11ea-82fd-6ce0bf433a80.jpg)

kerem commented

2026-03-16 13:33:14 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 23, 2019):

Check the root directory and if there exists a folder named .postwoman delete it. And again run npm run dev

That folder will be created at npm run dev.
Don't forget to close current localhost:3000 windows in browser if there any.

@liyasthomas commented on GitHub (Nov 23, 2019): Check the root directory and if there exists a folder named `.postwoman` delete it. And again run `npm run dev` That folder will be created at `npm run dev`. Don't forget to close current `localhost:3000` windows in browser if there any.

kerem commented

2026-03-16 13:33:19 +03:00

Author

Owner

@pierol commented on GitHub (Nov 23, 2019):

@pierol commented on GitHub (Nov 23, 2019): ![Untitled](https://user-images.githubusercontent.com/433875/69476891-cc9e0e80-0ddf-11ea-848a-640c6bd865ff.jpg)

kerem commented

2026-03-16 13:33:24 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 23, 2019):

I'll run some more tests and get back to you.

@liyasthomas commented on GitHub (Nov 23, 2019): I'll run some more tests and get back to you.

kerem commented

2026-03-16 13:33:29 +03:00

Author

Owner

@FatDoge commented on GitHub (Nov 25, 2019):

I meet the same problem, delete the .postwoman directory seems useless.
System infomation: Linux VM_202_150_centos 3.10.0-514.21.1.el7.x86_64
I use the cloud server offered by Tencent Cloud.

@FatDoge commented on GitHub (Nov 25, 2019): I meet the same problem, delete the ```.postwoman``` directory seems useless. System infomation: ```Linux VM_202_150_centos 3.10.0-514.21.1.el7.x86_64``` I use the cloud server offered by Tencent Cloud.

kerem commented

2026-03-16 13:33:34 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 25, 2019):

Issue has been identified. Will patch soon with a fix.

@liyasthomas commented on GitHub (Nov 25, 2019): Issue has been identified. Will patch soon with a fix.

kerem commented

2026-03-16 13:33:39 +03:00

Author

Owner

@FatDoge commented on GitHub (Nov 25, 2019):

.postwoman/version.json file is not normally generated in build.js. if you need to use it urgently, you can delete the corresponding import statement and the related code in layout/default.vue file first.(Unrecommended)

@FatDoge commented on GitHub (Nov 25, 2019): ```.postwoman/version.json``` file is not normally generated in ```build.js```. if you need to use it urgently, you can delete the corresponding import statement and the related code in ```layout/default.vue``` file first.(**Unrecommended**)

kerem commented

2026-03-16 13:33:44 +03:00

Author

Owner

@ghost commented on GitHub (Nov 25, 2019):

ths, please fix it cause i met also some issue like this.
or give me s solution to avoid this

@ghost commented on GitHub (Nov 25, 2019): ths, please fix it cause i met also some issue like this. or give me s solution to avoid this

kerem commented

2026-03-16 13:33:49 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 25, 2019):

We couldn't reproduce the issue at our end.
The .postwoman/version.json is created at npm run generate as well as at npm run build.

After investigating more, we think this might be an issue with the host system. Since this is device and architecture dependent, we need debug logs to find out what went wrong. Please provide that so that we could reproduce the issues at our end.

@liyasthomas commented on GitHub (Nov 25, 2019): We couldn't reproduce the issue at our end. The `.postwoman/version.json` is created at `npm run generate` as well as at `npm run build`. After investigating more, we think this might be an issue with the host system. Since this is device and architecture dependent, we need debug logs to find out what went wrong. Please provide that so that we could reproduce the issues at our end.

kerem commented

2026-03-16 13:33:54 +03:00

Author

Owner

@hosseinnedaee commented on GitHub (Nov 25, 2019):

npm run generate and npm run build woks for me on Ubuntu 18.04

@hosseinnedaee commented on GitHub (Nov 25, 2019): `npm run generate` and `npm run build` woks for me on Ubuntu 18.04

kerem commented

2026-03-16 13:34:00 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 25, 2019):

Our CI build is on Linux and it's working fine.
I can also confirm npm run generate works on Windows build 1803.

@liyasthomas commented on GitHub (Nov 25, 2019): Our CI build is on Linux and it's working fine. I can also confirm `npm run generate` works on Windows build 1803.

kerem commented

2026-03-16 13:34:05 +03:00

Author

Owner

@FatDoge commented on GitHub (Nov 26, 2019):

I just clone the code to my pc again.

> git clone https://github.com/liyasthomas/postwoman.git
> cd postwoman
> npm i
> npm run build

And everything is okay now...
Below is some information of my local enviroment:

> nvm version
1.1.7
> node -v
v12.0.0
> npm -v
v6.10.3

My PC OS is Windows10 Home Chinese Edition 1903.

That's weird, I can't repoduce the problem and I want to know why, I even change the local PC date to yestoday.
I will try again on my linux server and let us see if there is something strange.

The server works fine today.

@FatDoge commented on GitHub (Nov 26, 2019): I just clone the code to my pc again. ``` shell > git clone https://github.com/liyasthomas/postwoman.git > cd postwoman > npm i > npm run build ``` And everything is okay now... Below is some information of my local enviroment: ``` shell > nvm version 1.1.7 > node -v v12.0.0 > npm -v v6.10.3 ``` My PC OS is Windows10 Home Chinese Edition 1903. --- That's weird, I can't repoduce the problem and I want to know why, I even change the local PC date to yestoday. **I will try again on my linux server and let us see if there is something strange.** --- The server works fine today.

kerem commented

2026-03-16 13:34:10 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 26, 2019):

Usually these kinda errors happen when npm cache exists with lower version of dependencies. Delete node_modules, clean the cache, npm install again will solve most of it.

@liyasthomas commented on GitHub (Nov 26, 2019): Usually these kinda errors happen when npm cache exists with lower version of dependencies. Delete node_modules, clean the cache, npm install again will solve most of it.

kerem commented

2026-03-16 13:34:15 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 26, 2019):

Some workarounds:

Delete node_modules
npm cache clean
npm i
npm run build or npm run generate to build

If the above steps fails, try:

npm rebuild node-sass
npm run generate

@liyasthomas commented on GitHub (Nov 26, 2019): Some workarounds: 0. Delete node_modules 1. `npm cache clean` 2. `npm i` 3. `npm run build` or `npm run generate` to build If the above steps fails, try: 0. `npm rebuild node-sass` 1. `npm run generate`

kerem commented

2026-03-16 13:34:20 +03:00

Author

Owner

@NBTX commented on GitHub (Nov 26, 2019):

@liyasthomas I think this can be closed?

@NBTX commented on GitHub (Nov 26, 2019): @liyasthomas I think this can be closed?

kerem commented

2026-03-16 13:34:25 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 26, 2019):

This issue is stale and hence closing

@liyasthomas commented on GitHub (Nov 26, 2019): This issue is stale and hence closing

kerem commented

2026-03-16 13:34:30 +03:00

Author

Owner

@ccenjie commented on GitHub (Dec 19, 2019):

so , how to let it work, i do not see any solution,

Delete node_modules
npm cache clean
npm i
npm run dev or npm run generate
If the above steps fails, try:

npm rebuild node-sass
npm run generate

i do that, but no work

@ccenjie commented on GitHub (Dec 19, 2019): so , how to let it work, i do not see any solution, Delete node_modules npm cache clean npm i npm run dev or npm run generate If the above steps fails, try: npm rebuild node-sass npm run generate i do that, but no work

kerem commented

2026-03-16 13:34:35 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 19, 2019):

Is the error log as same as mentioned in this issue?

@liyasthomas commented on GitHub (Dec 19, 2019): Is the error log as same as mentioned in this issue?

kerem commented

2026-03-16 13:34:40 +03:00

Author

Owner

@NBTX commented on GitHub (Dec 19, 2019):

Just noticed in this case it may be because they downloaded a zip of the project rather than using git clone.

I believe the build script relies on the directory being a git repository in order to obtain certain information, so the project needs to be cloned rather than a ZIP file simply downloaded.

If I'm right though, I can just update the build script to accommodate this.

@NBTX commented on GitHub (Dec 19, 2019): Just noticed in this case it may be because they downloaded a zip of the project rather than using git clone. I believe the build script relies on the directory being a git repository in order to obtain certain information, so the project needs to be cloned rather than a ZIP file simply downloaded. If I'm right though, I can just update the build script to accommodate this.

kerem commented

2026-03-16 13:34:45 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 19, 2019):

@NBTX build.js is tailored for CI, remove git dependency / online version fetch and if possible, get version from package.json. Or else, completely comment out version section from footer. 👍

@liyasthomas commented on GitHub (Dec 19, 2019): @NBTX `build.js` is tailored for CI, remove git dependency / online version fetch and if possible, get version from `package.json`. Or else, completely comment out version section from footer. 👍

kerem commented

2026-03-16 13:34:51 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Feb 9, 2020):

Closing this issue as it seems to be fixed.

@AndrewBastin commented on GitHub (Feb 9, 2020): Closing this issue as it seems to be fixed.

kerem commented

2026-03-16 13:34:56 +03:00

Author

Owner

@Cedric4real commented on GitHub (Feb 20, 2020):

Cloning definetely solves the issue, thank you.

@Cedric4real commented on GitHub (Feb 20, 2020): Cloning definetely solves the issue, thank you.

Rows
Columns

[GH-ISSUE #327] Build failed #122