hyperstack-org / hyperstack

Hyperstack ALPHA https://hyperstack.org
https://docs.hyperstack.org
MIT License
540 stars 41 forks source link

Installation with the template: application.js does not appear to exist #278

Open vindarel opened 4 years ago

vindarel commented 4 years ago

Hi,

I'm trying to follow the installation instructions from the website.

This commands:

rails new hyperstacktest -T -m https://rawgit.com/hyperstack-org/hyperstack/edge/install/rails-webpacker.rb

ends with

…
yarn add v1.19.0
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─ jquery@3.4.1
info All dependencies
└─ jquery@3.4.1
Done in 1.43s.
      insert    app/assets/javascripts/application.js
The template [https://rawgit.com/hyperstack-org/hyperstack/edge/install/rails-webpacker.rb] could not be loaded. Error: The file /home/vince/bacasable/hyperstacktest/app/assets/javascripts/application.js does not appear to exist

I try to carry on:

Looks like there's a missing bit in the template.

Cheers

Rails 6

ps: could you point to real world examples, preferably open source (apart from the website itself), if there are any?

barriehadfield commented 4 years ago

hi @vindarel we have not yet tested on Rails 6. I will get that done in the next few days. You might want to give it a spin with the non-template installer, it might just work... I think the issue is that a lot of the rails < 6 has to do with Webpacker which is now included.

tansaku commented 4 years ago

I had a go at doing that and got this:

Bundler could not find compatible versions for gem "rails":
  In snapshot (Gemfile.lock):
    rails (= 6.0.2.1)

  In Gemfile:
    rails (~> 6.0.2, >= 6.0.2.1)

rails-hyperstack (~> 1.0.alpha1.0) was resolved to 1.0.alpha1.5, which
depends on
      opal-rails (~> 0.9.4) was resolved to 0.9.5, which depends on
        rails (>= 4.1, < 6.0)

rails-hyperstack (~> 1.0.alpha1.0) was resolved to 1.0.alpha1.5, which
depends on
      rails (>= 4.0.0)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
tansaku commented 4 years ago

I ran bundle update but got the same issue ...

backward-crazy-mage-puppy-36 commented 4 years ago

Facing the same issue with rails 6.