質問編集履歴
3
タイトル修正
test
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
herokuで
|
|
1
|
+
herokuでデプロイ作業中のgit push heroku masterでPrecompiling assets failed.エラーが出てしまう。
|
test
CHANGED
|
File without changes
|
2
herokuの登録しているappを削除後、再度作成。その後エラー内容が変わったので修正しました。
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -14,6 +14,118 @@
|
|
|
14
14
|
|
|
15
15
|
```
|
|
16
16
|
|
|
17
|
+
|
|
18
|
+
|
|
19
|
+
remote: Compressing source files... done.
|
|
20
|
+
|
|
21
|
+
remote: Building source:
|
|
22
|
+
|
|
23
|
+
remote:
|
|
24
|
+
|
|
25
|
+
remote: -----> Building on the Heroku-20 stack
|
|
26
|
+
|
|
27
|
+
remote: ! Warning: Multiple default buildpacks reported the ability to handle this app. The first buildpack in the list below will be used.
|
|
28
|
+
|
|
29
|
+
remote: Detected buildpacks: Ruby,Node.js
|
|
30
|
+
|
|
31
|
+
remote: See https://devcenter.heroku.com/articles/buildpacks#buildpack-detect-order
|
|
32
|
+
|
|
33
|
+
remote: -----> Ruby app detected
|
|
34
|
+
|
|
35
|
+
remote: -----> Installing bundler 2.2.11
|
|
36
|
+
|
|
37
|
+
remote: -----> Removing BUNDLED WITH version in the Gemfile.lock
|
|
38
|
+
|
|
39
|
+
remote: -----> Compiling Ruby/Rails
|
|
40
|
+
|
|
41
|
+
remote: -----> Using Ruby version: ruby-2.6.6
|
|
42
|
+
|
|
43
|
+
remote: -----> Installing dependencies using bundler 2.2.11
|
|
44
|
+
|
|
45
|
+
remote: Running: BUNDLE_WITHOUT='development:test' BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 bundle install -j4
|
|
46
|
+
|
|
47
|
+
remote: Fetching gem metadata from https://rubygems.org/............
|
|
48
|
+
|
|
49
|
+
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
|
|
54
|
+
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
remote: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
|
|
58
|
+
|
|
59
|
+
remote: [1/4] Resolving packages...
|
|
60
|
+
|
|
61
|
+
remote: [2/4] Fetching packages...
|
|
62
|
+
|
|
63
|
+
remote: info fsevents@2.3.1: The platform "linux" is incompatible with this module.
|
|
64
|
+
|
|
65
|
+
remote: info "fsevents@2.3.1" is an optional dependency and failed compatibility check. Excluding it from installation.
|
|
66
|
+
|
|
67
|
+
remote: info fsevents@1.2.13: The platform "linux" is incompatible with this module.
|
|
68
|
+
|
|
69
|
+
remote: info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
|
|
70
|
+
|
|
71
|
+
remote: [3/4] Linking dependencies...
|
|
72
|
+
|
|
73
|
+
remote: warning " > vue-loader@15.9.6" has unmet peer dependency "css-loader@*".
|
|
74
|
+
|
|
75
|
+
remote: [4/4] Building fresh packages...
|
|
76
|
+
|
|
77
|
+
remote: Done in 33.77s.
|
|
78
|
+
|
|
79
|
+
remote: yarn install v1.22.4
|
|
80
|
+
|
|
81
|
+
remote: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
|
|
82
|
+
|
|
83
|
+
remote: [1/4] Resolving packages...
|
|
84
|
+
|
|
85
|
+
remote: [2/4] Fetching packages...
|
|
86
|
+
|
|
87
|
+
remote: info fsevents@2.3.1: The platform "linux" is incompatible with this module.
|
|
88
|
+
|
|
89
|
+
remote: info "fsevents@2.3.1" is an optional dependency and failed compatibility check. Excluding it from installation.
|
|
90
|
+
|
|
91
|
+
remote: info fsevents@1.2.13: The platform "linux" is incompatible with this module.
|
|
92
|
+
|
|
93
|
+
remote: info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
|
|
94
|
+
|
|
95
|
+
remote: [3/4] Linking dependencies...
|
|
96
|
+
|
|
97
|
+
remote: warning " > vue-loader@15.9.6" has unmet peer dependency "css-loader@*".
|
|
98
|
+
|
|
99
|
+
remote: [4/4] Building fresh packages...
|
|
100
|
+
|
|
101
|
+
remote: Done in 6.37s.
|
|
102
|
+
|
|
103
|
+
|
|
104
|
+
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
|
|
108
|
+
|
|
109
|
+
|
|
110
|
+
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
remote: Compiling...
|
|
114
|
+
|
|
115
|
+
remote: Compilation failed:
|
|
116
|
+
|
|
117
|
+
remote: CLI for webpack must be installed.
|
|
118
|
+
|
|
119
|
+
remote: webpack-cli (https://github.com/webpack/webpack-cli)
|
|
120
|
+
|
|
121
|
+
remote:
|
|
122
|
+
|
|
123
|
+
remote: We will use "yarn" to install the CLI via "yarn add -D webpack-cli".
|
|
124
|
+
|
|
125
|
+
remote: Do you want to install 'webpack-cli' (yes/no):
|
|
126
|
+
|
|
127
|
+
remote:
|
|
128
|
+
|
|
17
129
|
remote: !
|
|
18
130
|
|
|
19
131
|
remote: ! Precompiling assets failed.
|
|
@@ -26,47 +138,19 @@
|
|
|
26
138
|
|
|
27
139
|
remote: ! Push failed
|
|
28
140
|
|
|
29
|
-
remote: !
|
|
30
|
-
|
|
31
|
-
remote: ! ## Warning - The same version of this code has already been built: c06700a8897f94df83f06d3423a2796bba7c60ce
|
|
32
|
-
|
|
33
|
-
remote: !
|
|
34
|
-
|
|
35
|
-
remote: ! We have detected that you have triggered a build from source code with version c06700a8897f94df83f06d3423a2796bba7c60ce
|
|
36
|
-
|
|
37
|
-
remote: ! at least twice. One common cause of this behavior is attempting to deploy code from a different branch.
|
|
38
|
-
|
|
39
|
-
remote: !
|
|
40
|
-
|
|
41
|
-
remote: ! If you are developing on a branch and deploying via git you must run:
|
|
42
|
-
|
|
43
|
-
remote: !
|
|
44
|
-
|
|
45
|
-
remote: ! git push heroku <branchname>:main
|
|
46
|
-
|
|
47
|
-
remote: !
|
|
48
|
-
|
|
49
|
-
remote: ! This article goes into details on the behavior:
|
|
50
|
-
|
|
51
|
-
remote: ! https://devcenter.heroku.com/articles/duplicate-build-version
|
|
52
|
-
|
|
53
|
-
remote:
|
|
54
|
-
|
|
55
141
|
remote: Verifying deploy...
|
|
56
142
|
|
|
57
143
|
remote:
|
|
58
144
|
|
|
59
|
-
remote: ! Push rejected to storemanual.
|
|
145
|
+
remote: ! Push rejected to store-manual.
|
|
60
146
|
|
|
61
147
|
remote:
|
|
62
148
|
|
|
63
|
-
To https://git.heroku.com/storemanual.git
|
|
149
|
+
To https://git.heroku.com/store-manual.git
|
|
64
150
|
|
|
65
151
|
! [remote rejected] master -> master (pre-receive hook declined)
|
|
66
152
|
|
|
67
|
-
error: failed to push some refs to 'https://git.heroku.com/storemanual.git'
|
|
153
|
+
error: failed to push some refs to 'https://git.heroku.com/store-manual.git'
|
|
68
|
-
|
|
69
|
-
|
|
70
154
|
|
|
71
155
|
```
|
|
72
156
|
|
|
@@ -74,9 +158,11 @@
|
|
|
74
158
|
|
|
75
159
|
### 試してみた事
|
|
76
160
|
|
|
77
|
-
- git add .を行い、git commit -m "first commit"を行いgit pushしました
|
|
161
|
+
- git add .を行い、git commit -m "first commit"を行いgit pushしました。
|
|
78
162
|
|
|
163
|
+
- git push heroku <branchname>:mainというエラーが発生。
|
|
79
164
|
|
|
165
|
+
- herokuの中の登録しているappを削除し、再度heroku createその後アプリ名を変更した事による整合性を一致させる為、git remote rm herokuを行い、heroku git:remote -aを行いました。
|
|
80
166
|
|
|
81
167
|
|
|
82
168
|
|
1
試してみた事を追記
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -72,6 +72,14 @@
|
|
|
72
72
|
|
|
73
73
|
|
|
74
74
|
|
|
75
|
+
### 試してみた事
|
|
76
|
+
|
|
77
|
+
- git add .を行い、git commit -m "first commit"を行いgit pushしましたが 同様のエラーが発生しました。
|
|
78
|
+
|
|
79
|
+
|
|
80
|
+
|
|
81
|
+
|
|
82
|
+
|
|
75
83
|
### 補足情報（FW/ツールのバージョンなど）
|
|
76
84
|
|
|
77
85
|
|