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
Error: WebPack #28
Comments
I am having the same issue |
Seems like some sort of dev dependency issue... I probably broke something in package.jsom. I admit node and Babel stuff isn’t my strong suit, but I’ll see if I can reproduce and figure it out this weekend. In the meantime, can you tell me your version of node and n0pm? |
I believe I found the culprit... the babel config was referencing an unnecessary preset. Please update to version 1.7.1 and see if that resolves the issue. Thanks! |
@richardtallent thanks for taking a look at this. Upgrading it on my end did not work. Hre is my log file 0 info it worked if it ends with ok |
Also this is the error when building ERROR Failed to compile with 1 errors 8:59:56 AM error /js/app.01fb2841f5c492f53950.js from UglifyJs |
What does your babel config look like? The second error suggests your environment isn't set up to build from ES6 / ECMAScript 2015 source code, since it's bailing on the shorthand notation for function declaration in the mixin. We have the same version of npm, I'm using an older version of node but I can't imagine that would be the issue. Reopening until we can figure it out... |
Follow-up -- I just spent a few hours rebuilding my other component, vue-stars, because I was having trouble using it as well in a separate app. Decided to split the component from the sample app so the resulting npm package is dirt-easy to use. I think I'm going to do the same with this one. I'm still not exactly sure what the problem is, but I have some suspicions and I think this will clear up the issue. |
I've split up the calendar component from its sample app... painful but I think necessary, the PWA template used for the sample app just isn't good for publishing a component. Please give the latest version a shot (1.8.1, live on npm). Your import and require statements should be adjusted (see the readme for the current sample code). I'll leave this open until you can confirm it's working... |
@richardtallent Thanks for working on this! I will work on getting it updated on my end to see if we can build. We were able to build for production by manually running the mixin-calendarMath.js through a babel compiler then putting the file back in. Obviously not a good long-term solution for us, but allowed us to deploy. I really appreciate you working on this fix for us! |
@richardtallent Works Fine thank's ! |
Hello,
I try to use your calendar but I get:
ERROR in ./node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]],"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0&bustCache!./node_modules/vue-simple-calendar/src/components/calendar-month.vue Module build failed: Error: Couldn't find preset "stage-2" relative to directory "C:\\Users\\umignon\\projects\\capability\\node_modules\\vue-simple-calendar" at C:\Users\umignon\projects\capability\node_modules\babel-core\lib\transformation\file\options\option-manager.js:293:19 at Array.map (<anonymous>) at OptionManager.resolvePresets (C:\Users\umignon\projects\capability\node_modules\babel-core\lib\transformation\file\options\option-manager.js:275:20) at OptionManager.mergePresets (C:\Users\umignon\projects\capability\node_modules\babel-core\lib\transformation\file\options\option-manager.js:264:10) at OptionManager.mergeOptions (C:\Users\umignon\projects\capability\node_modules\babel-core\lib\transformation\file\options\option-manager.js:249:14) at OptionManager.init (C:\Users\umignon\projects\capability\node_modules\babel-core\lib\transformation\file\options\option-manager.js:368:12) at File.initOptions (C:\Users\umignon\projects\capability\node_modules\babel-core\lib\transformation\file\index.js:212:65) at new File (C:\Users\umignon\projects\capability\node_modules\babel-core\lib\transformation\file\index.js:135:24) at Pipeline.transform (C:\Users\umignon\projects\capability\node_modules\babel-core\lib\transformation\pipeline.js:46:16) at transpile (C:\Users\umignon\projects\capability\node_modules\babel-loader\lib\index.js:50:20) at C:\Users\umignon\projects\capability\node_modules\babel-loader\lib\fs-cache.js:118:18 at ReadFileContext.callback (C:\Users\umignon\projects\capability\node_modules\babel-loader\lib\fs-cache.js:31:21) at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:421:13) @ ./node_modules/vue-simple-calendar/src/components/calendar-month.vue 8:21-364 @ ./node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]],"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0&bustCache!./resources/assets/js/components/fullCalendar.vue @ ./resources/assets/js/components/fullCalendar.vue @ ./resources/assets/js/vue.js @ ./resources/assets/js/app.js @ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! @ development:
cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the @ development 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\umignon\AppData\Roaming\npm-cache_logs\2017-12-15T14_48_05_818Z-debug.log
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.`
here is my app.vue:
here is my app.js:
Thanks for your replys !
The text was updated successfully, but these errors were encountered: