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

Can't install svelte #2212

Closed
frostmark opened this issue Aug 4, 2019 · 5 comments
Closed

Can't install svelte #2212

frostmark opened this issue Aug 4, 2019 · 5 comments

Comments

@frostmark
Copy link

frostmark commented Aug 4, 2019

When I try to install svelte bundle exec rails webpacker:install:svelte then I catch follow error:

rails aborted!
Don't know how to build task 'webpacker:install:svelte' (See the list of available tasks with `rails --tasks`)
Did you mean?  webpacker:install:elm
               webpacker:install:vue
               webpacker:install:react
               webpacker:install:erb
               webpacker:install:coffee
               webpacker:install:stimulus
               webpacker:install:angular

@magiknono
Copy link

magiknono commented Aug 5, 2019

i tested with rails 5.2 and rails 6.0.0.rc2 with webpacker 4.0.7 but it did not works and i had the same error.
And with rails --tasks in terminal, i don't see entry that references webpacker:install:svelte

Here is my repo to make it works manually sveltewithwebpack

I only followed steps of the PR #2134 by @victorhazbun and this commit

@frostmark
Copy link
Author

@magiknono it's because of the new version not released yet. I installed the gem from git master and it works for me

@smondal
Copy link
Contributor

smondal commented Aug 6, 2019

As rails 6 were release and rails are using webpacker by default, So I think we should also release webapacker. So all the latest changes will reflect in the new version.

@victorhazbun
Copy link
Contributor

Here is a sample app, Svelte and Rails 5 https://github.com/victorhazbun/fish-hub

@frostmark
Copy link
Author

I close this issue because I think that it's will be fixed when published the next version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants