Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug when starting build #249

Open
vadim9999 opened this issue Jun 23, 2019 · 4 comments
Open

Bug when starting build #249

vadim9999 opened this issue Jun 23, 2019 · 4 comments
Assignees
Labels
bug Something isn't working dependencies Pull requests that update a dependency file help wanted Extra attention is needed high

Comments

@vadim9999
Copy link
Collaborator

vadim9999 commented Jun 23, 2019

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:
sudo npm run build

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@groceristar/pdf-export@1.2.0 prebuild /home/vadim/work/javascript/pdf-export-component
npm run std --silent

internal/modules/cjs/loader.js:638
throw err;
^

Error: Cannot find module 'prelude-ls'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:690:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/home/vadim/work/javascript/pdf-export-component/node_modules/levn/lib/parse-string.js:4:12)
at Object. (/home/vadim/work/javascript/pdf-export-component/node_modules/levn/lib/parse-string.js:113:4)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)

@groceristar/pdf-export@1.2.0 build /home/vadim/work/javascript/pdf-export-component
rollup -c config/prod.js

Error: ENOENT: no such file or directory, lstat '/home/vadim/work/javascript/pdf-export-component/config/prod.js'
at Object.realpathSync (fs.js:1461:7)
at runRollup (/home/vadim/work/javascript/pdf-export-component/node_modules/rollup/bin/rollup:3929:20)
at Object. (/home/vadim/work/javascript/pdf-export-component/node_modules/rollup/bin/rollup:4014:2)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
at startup (internal/bootstrap/node.js:283:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @groceristar/pdf-export@1.2.0 build: rollup -c config/prod.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @groceristar/pdf-export@1.2.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! /home/vadim/.npm/_logs/2019-06-23T20_34_48_241Z-debug.log

@atherdon
Copy link
Member

can you try a downgraded version of this module as well? maybe it will help.

I think it because Eugene decide to build code with rollup only, without using babel at all...

@vadim9999
Copy link
Collaborator Author

FIrst error I have fixed with adding eslint second with replacing prod on product

@vadim9999
Copy link
Collaborator Author

Now I have !] (babel plugin) Error: Plugin/Preset files are not allowed to export objects, only functions. In /home/vadim/work/javascript/pdf-export-component/node_modules/babel-preset-es2015/lib/index.js
or after deleting babel-preset-es2015 It's sends error that can't find it

@atherdon
Copy link
Member

i assume we should leave this error to Eugene. Because he started to mess with rollup. and he should finish it.

try a prev version please, because i think it'll help - because before i didn't experience this error.

Actually, this is one of the perfect example of why i fucking love this modularity approach(and i want to do it more and more). Because we can really easily to locate a source of a problem. just imagine if all fetch, backend, react were messed up in one place and when something crashing - it went down the whole project at one time

@atherdon atherdon added bug Something isn't working dependencies Pull requests that update a dependency file help wanted Extra attention is needed high labels Jun 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dependencies Pull requests that update a dependency file help wanted Extra attention is needed high
Projects
None yet
Development

No branches or pull requests

3 participants