-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathscully.log
More file actions
184 lines (136 loc) · 9.79 KB
/
scully.log
File metadata and controls
184 lines (136 loc) · 9.79 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
(You can skip this, or any future question by using the --noPrompt flag)
handleUnknownRoute: "/blog/blog-post-1/index.html", 404:""
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
----------------------------------Using stored unhandled routes!. To discover new routes in the angular app use "npx scully --scanRoutes"----------------------------------
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
----------------------------------Using stored unhandled routes!. To discover new routes in the angular app use "npx scully --scanRoutes"----------------------------------
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
----------------------------------Using stored unhandled routes!. To discover new routes in the angular app use "npx scully --scanRoutes"----------------------------------
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
----------------------------------Using stored unhandled routes!. To discover new routes in the angular app use "npx scully --scanRoutes"----------------------------------
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
----------------------------------Using stored unhandled routes!. To discover new routes in the angular app use "npx scully --scanRoutes"----------------------------------
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
----------------------------------Using stored unhandled routes!. To discover new routes in the angular app use "npx scully --scanRoutes"----------------------------------
Folder "./scully" doesn't seem to contain custom plugins Deprecation Notice:
======================================================================
From now on, the plugin that is being used to render a route is
able to be changed by the user. You can do this by adding or
enabling the plugin your scully.portfolio.config.ts
file. For your convenience, we loaded the Puppeteer plugin for you.
To disable this warning enable the plugin of your choice.
for Puppeteer please add:
import '@scullyio/scully-plugin-puppeteer';
to your scully.portfolio.config.ts file.
When you get this warning while not using scully-plugin-puppeteer
you need to set the defaultRouteRenderer to the name of your plugin.
The defaultRouteRenderer is now set to 'routeRenderer'.
======================================================================
(You can skip this, or any future question by using the --noPrompt flag)
----------------------------------Using stored unhandled routes!. To discover new routes in the angular app use "npx scully --scanRoutes"----------------------------------