mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #383] File js/main.js is not created? #279
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#279
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @baoc75 on GitHub (Jul 26, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/383
Well I run the
npm install, but in ending step "Fetching Version Source File" it said thatpublic\js\main.jsnot found. I have tried to reinstall npm stuff for many times but it doesn't fix.Because of that, when I trying to access Koel, it's show a message:
@BernardGoldberger commented on GitHub (Jul 27, 2016):
Can you take us through your install process from the start? include Koel version and OS.
@baoc75 commented on GitHub (Jul 28, 2016):
Here is my process:
@BernardGoldberger commented on GitHub (Jul 28, 2016):
Can you please provide the entire output of
npm install.On another note if you are setting up Koel for the first time, you should be running
composer installand thenphp artisan koel:init, see https://github.com/phanan/koel/wiki#installation.My working theory is that either the file is not being created or that for some reason the permissions get messed up.
@X-Ryl669 commented on GitHub (Jul 28, 2016):
I think it's because notify-send is not installed in the default npm installation.
So the short term fix is to call
sudo npm install -g notify-sendthensudo apt-get install libnotify-binand then, finally "npm install"@baoc75 commented on GitHub (Jul 29, 2016):
@bdgold @X-Ryl669 Thanks for your help but it doesn't work. Here is my npm install output
npmlog.txt
Although few packpage need to update to newer version.
@BernardGoldberger commented on GitHub (Jul 29, 2016):
[08:42:29] gulp-notify: [Laravel Elixir] Browserify Failed!: Unexpected tokenDelete the
node_modulesfolder and runnpm installagain, I don't know that it will fix it but its a start.@BernardGoldberger commented on GitHub (Jul 29, 2016):
@baoc75 I'm not sure what you setup is but you should separate projects to their own folders.
Currently you have Koel in the htdocs root folder, you should create a sub-folder for Koel. Git or Composer would take care of that if you use either of them.
@X-Ryl669 commented on GitHub (Jul 29, 2016):
I've the same error as you, and I think it's going to prevent a lot of people starting from scratch on a debian Jessie system (following the tutorial given)
The syntax in app.vue does not get parsed correctly, thus main.js is not generated, here's the callstack when the error is thrown:
@BernardGoldberger commented on GitHub (Jul 29, 2016):
This guy seems to have had the exact same issue and solved it by adding a line.
I'm not sure how it all adds up though especially since most of us are not having this issue, and I'm not sure why he had to add it.
Its most likely an issue with one of the packages and not Koel, try researching https://github.com/laravel/elixir/issues.
@X-Ryl669 commented on GitHub (Jul 29, 2016):
Right! I've been struggling for hours on this one. You need to add
in the gulpfile.js, and then it compiles. But it fails later on... set issue #385
@X-Ryl669 commented on GitHub (Jul 31, 2016):
Can someone with a working configuration post the output of these commands: ?
The last command gave me:
@BernardGoldberger commented on GitHub (Jul 31, 2016):
node v6.2.2npm 3.9.5npm listIssue 383 - npm list.txt@phanan commented on GitHub (Jul 31, 2016):
@X-Ryl669 Try upgrading your node to at least v5.5.0 and see if the problem persists.
@alex-irt commented on GitHub (Jul 31, 2016):
I ran into the same issue today and upgrading to node v6.3.1 has everything working now. Thanks for the great support!
@X-Ryl669 commented on GitHub (Aug 1, 2016):
Same for me, that was it. I've posted a comment on the "unofficial debian installation guide" page, as it should be changed as well.
@phanan commented on GitHub (Aug 1, 2016):
Glad it works for you guys. Closing this issue now.
trackin DB migration #1203