Installation SASS, message sur terminal windows

Version imprimable

27/05/2020, 19h03
haddocks

1 pièce(s) jointe(s)

Installation SASS, message sur terminal windows

Bonjour,

Je viens d'installer "sass" avec npm et voici les messages retournés par le terminal:
Pièce jointe 568456

Le moins qu'on puisse dire, c'est que c'est pas très claire pour un débutant:calim2:, alors est ce quelqu'un pourrait me dire quelles actions je dois faire ?

D'avance merci.
27/05/2020, 19h45
Marco46

Il faudrait aussi savoir ce que te demande exactement ton cours open class room.

Il faudrait aussi connaître les versions de node et npm installées sur ta machine (node -v et npm -v dans un terminal)

Tu as installé ce package qui est à priori lié à Dart, c'est ce que tu voulais ?

Pour le reste, les messages indiquent que :
- tu n'as pas initialisé correctement un package.json (npm init dans un terminal) avant d'exécuter l'installation mais ça ne semble pas bloquant (warning et pas erreur)
- il t'a créé un package-lock.json lors de l'installation de sass ce qui est normal, il te faudra commit ce fichier avec le reste
- le package fsevents qui doit être une dépendance de sass ne supporte pas ta plateforme (ton OS), je ne sais pas ce que ça peut donner à l'exécution
- les 4 derniers warnings concernent le détail de ton package.json qui n'est pas correctement initialisé (il te dit que certains champs sont absents alors qu'il est de bon ton de les remplir) mais rien de bloquant.

Donc au final tout dépend de ce qui est demandé dans ton cours. A priori tu devrais pouvoir le continuer normalement il n'y a pas d'erreurs seulement des warnings.
27/05/2020, 21h28
haddocks

Merci pour toutes ces infos.

Le cours en question ne donne pas de version, il dit seulement a quoi ça va servir.

Ce que j'ai installé:
Node js: 14.3.0
npm: 6.14.5
sass: 1.26.5

Si "commit" veut dire valider, alors comment fait-on pour valider le fichier Package-lock.json ?
Et enfin, comment fait-on pour remplir les champs du fichier package.json ?

Merci encore.
27/05/2020, 23h14
Marco46

Commit c'est lié à Git, cf la FAQ. Pour les besoins de ton tuto tu peux ignorer ça et ignorer le package-lock.json.

Pour modifier les champs du package.json ben tu ouvres le fichier et tu les modifies.

Ca n'a rien d'obligatoire, il s'agit de warnings pas d'erreurs.

Tu es bloqué quelque part ? Pour moi tu peux tout simplement continuer ton tuto sans te préoccuper de ces messages.
28/05/2020, 12h58
haddocks

Merci Marco46,
Je vais avancer et je verrai comme t'as dit.
28/05/2020, 20h17
haddocks

2 pièce(s) jointe(s)

Bonjour,

J'y suis presque mais ça bloque à cette étape:
Pièce jointe 568716

et voilà ce que j'obtiens:
Pièce jointe 568720

Sass est pourtant bien installé :weird:
28/05/2020, 20h48
haddocks

1 pièce(s) jointe(s)

Par curiosité j'ai tester un "sass --version" à la racine et dans mon repertoire:(
Çà colle pas avec la photo au début du poste qui dit que sass est bien installé. j'ai même le fichier Package-lock.jason.
Pièce jointe 568729
28/05/2020, 22h43
Marco46
Ton OS ne détecte pas les modules installés dans ton-projet\node_modules\.bin\ (problème de PATH).

Place toi à la racine de ton projet et essaie d'exécuter node node_modules\.bin\sass --version.

Sinon le plus simple reste d'ajouter un script dans ton package.json. Tu dois y avoir une section "scripts" tu lui en ajoutes un :
Code:

1 2 3 4 "scripts": { "sass": "sass --version" },
que tu exécutes via ton IDE ou dans ta console en te plaçant à la racine du projet puis npm run sass.

Si ça marche tu peux y ajouter la commande initialement souhaitée :
Code:

1 2 3 4 5 "scripts": { "sass": "sass --version", "sass::watch": "sass --watch scss:css" },
Que tu exécutes via npm run sass::watch.

Sinon dans tes posts évite les screenshots, poste plutôt des copiés / collés de la console c'est plus simple à traiter derrière.

Bonjour Marco46,

1- node node_modules\.bin\sass --version.

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom> node node_modules\.bin\sass --version
C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom\node_modules\.bin\sass:2
basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
          ^^^^^^^
 
SyntaxError: missing ) after argument list
[90m    at wrapSafe (internal/modules/cjs/loader.js:1116:16)[39m
[90m    at Module._compile (internal/modules/cjs/loader.js:1164:27)[39m
[90m    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1220:10)[39m
[90m    at Module.load (internal/modules/cjs/loader.js:1049:32)[39m
[90m    at Function.Module._load (internal/modules/cjs/loader.js:937:14)[39m
[90m    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)[39m
[90m    at internal/main/run_main_module.js:17:47[39m

2- Dans "package.json", j'ai copié la ligne 8 à la ligne 13.

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
{
  "name": "projet-bootstrap-openclassroom",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "dependencies": {
    "bootstrap": "^4.5.0",
    "sass": "^1.26.5"
  },
  "devDependencies": {},
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
    "sass": "^1.26.5"
  },
  "author": "",
  "license": "ISC"
}

3- npm run sass - executé dans powershell:

Code:

1
2
3
4
5
6
7
8
9
10
11
12
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom> npm run sass
npm ERR! code EJSONPARSE
npm ERR! file C:\Users\haddo.\Documents\CODEUR\Projet-bootstrap-openclassroom\package.json
npm ERR! JSON.parse Failed to parse json
npm ERR! JSON.parse Unexpected string in JSON at position 287 while parsing '{
npm ERR! JSON.parse   "name": "projet-bootstrap-openclassr'
npm ERR! JSON.parse Failed to parse package.json data.
npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript.
 
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\haddo\AppData\Roaming\npm-cache\_logs\2020-05-29T10_20_45_215Z-debug.log
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom>

Donc je suis pas allé plus loin.:?

30/05/2020, 13h16
Marco46
Quand tu as une erreur npm ERR! code EJSONPARSE sur ton package.json c'est que tu t'es planté quelque part en le modifiant.

Ici tu as oublié la virgule pour séparer la nouvelle entrée que tu as ajouté aux scripts.

Avant
Code:

1 2 3 4 5 "scripts": { "test": "echo \"Error: no test specified\" && exit 1" "sass": "^1.26.5" },
Après avec correction
Code:

1 2 3 4 5 "scripts": { "test": "echo \"Error: no test specified\" && exit 1", "sass": "^1.26.5" },
Pour ton point n°1 tu dois avoir un problème avec ton installation de node / npm sous windows, ça ressemble beaucoup à ça. Il faut savoir que la plateforme standard pour développer en web c'est linux et pas windows. Beaucoup de packages sont très mal testés sous windows donc utiliser cet OS c'est prendre un certain risque.

Je me rends compte à la relecture que tu n'as pas compris ce qu'il fallait mettre dans ton script.

Il te faut mettre plutôt
Code:

1 2 3 4 5 "scripts": { "test": "echo \"Error: no test specified\" && exit 1", "sass": "sass --version" },
et non la version du package qui ne sert que dans la propriété dependencies.

Si ça fonctionne tu peux ajouter la commande de watch :
Code:

1 2 3 4 5 6 "scripts": { "test": "echo \"Error: no test specified\" && exit 1", "sass": "sass --version", "sass::watch": "sass --watch scss:css" },

Bonjour Marco46,
:ptdr:
voila le json:

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
{
  "name": "projet-bootstrap-open classroom",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "dependencies": {
    "bootstrap": "^4.5.0",
    "sass": "^1.26.5"
  },
  "devDependencies": {},
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "sass": "sass --version"
  },
  "author": "",
  "license": "ISC"
}

Nouvelle tantative:

Code:

1
2
3
4
5
6
7
8
9
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom> sass --watch scss:css
sass : Le terme «sass» n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script ou programme
exécutable. Vérifiez l'orthographe du nom, ou si un chemin d'accès existe, vérifiez que le chemin d'accès est correct
et réessayez.
Au caractère Ligne:1 : 1
+ sass --watch scss:css
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (sass:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Un controle des versions:

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom> node -v
v14.3.0
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom> npm -v
6.14.5
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom> sass -v
sass : Le terme «sass» n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script ou programme
exécutable. Vérifiez l'orthographe du nom, ou si un chemin d'accès existe, vérifiez que le chemin d'accès est correct
et réessayez.
Au caractère Ligne:1 : 1
+ sass -v
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (sass:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
 
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom>

J'ai tenter de réinstaller npm:

Code:

1
2
3
4
5
6
7
8
9
10
11
12
PS C:\> npm update
PS C:\> npm install -g npm
npm ERR! code EEXIST
npm ERR! path C:\Program Files\nodejs\npm.cmd
npm ERR! Refusing to delete C:\Program Files\nodejs\npm.cmd: is outside C:\Program Files\nodejs\node_modules\npm and not a link
npm ERR! File exists: C:\Program Files\nodejs\npm.cmd
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.
 
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\haddo\AppData\Roaming\npm-cache\_logs\2020-05-30T12_58_10_808Z-debug.log
PS C:\> cd Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom

Je voudrait bien recommencer l'install de tous ça en te montrant ce qu'il se passe à chaque étape, mais comment remettre tout à plat ?:calim2:;)

30/05/2020, 17h43
Marco46

Désinstalle et réinstalle node (et pas npm qui est contenu dans node), tu as clairement un soucis à l'installation sur la gestion du PATH.
31/05/2020, 11h40
haddocks

Bonjour Marco46,

Je vais laisser ça de côté un moment, j'ai d'autres choses sur lesquels je voudrais avancer.

Merci.

2 pièce(s) jointe(s)

Bonjour,

j'ai pas trouvé comment désinstaller NodeJS.
j'ai lancé un fichier msi de cette adresse:
https://www.npmjs.com/get-npm

J'ai sélectionner l'option "installer les outils"

Pièce jointe 569332

voilà le fil du reste de l'install:

Code:

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
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
Getting latest version of the Chocolatey package for download.
Getting Chocolatey from https://chocolatey.org/api/v2/package/chocolatey/0.10.15.
Downloading 7-Zip commandline tool prior to extraction.
Extracting C:\Users\haddo\AppData\Local\Temp\chocolatey\chocInstall\chocolatey.zip to C:\Users\haddo\AppData\Local\Temp\chocolatey\chocInstall...
Installing chocolatey on this machine
Creating ChocolateyInstall as an environment variable (targeting 'Machine')
  Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'
WARNING: It's very likely you will need to close and reopen your shell
  before you can use choco.
Restricting write permissions to Administrators
We are setting up the Chocolatey package repository.
The packages themselves go to 'C:\ProgramData\chocolatey\lib'
  (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin'
  and points to an executable in 'C:\ProgramData\chocolatey\lib\yourPackageName'.
 
Creating Chocolatey folders if they do not already exist.
 
WARNING: You can safely ignore errors related to missing log files when
  upgrading from a version of Chocolatey less than 0.9.9.
  'Batch file could not be found' is also safe to ignore.
  'The system cannot find the file specified' - also safe.
chocolatey.nupkg file not installed in lib.
 Attempting to locate it from bootstrapper.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
AVERTISSEMENT*: Not setting tab completion: Profile file does not exist at
'C:\Users\haddo\OneDrive\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1'.
Chocolatey (choco.exe) is now ready.
You can call choco from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles
 first prior to using choco.
Ensuring chocolatey commands are on the path
Ensuring chocolatey.nupkg is in the lib folder
Chocolatey v0.10.15
Upgrading the following packages:
python;visualstudio2017-workload-vctools
By upgrading you accept licenses for the packages.
python is not installed. Installing...
Progress: Downloading python3 3.8.3... 100%
Progress: Downloading python3 3.8.3... 100%
Progress: Downloading chocolatey-core.extension 1.3.5.1... 100%
Progress: Downloading chocolatey-core.extension 1.3.5.1... 100%
Progress: Downloading vcredist2015 14.0.24215.20170201... 100%
Progress: Downloading vcredist2015 14.0.24215.20170201... 100%
Progress: Downloading vcredist140 14.26.28720.3... 100%
Progress: Downloading vcredist140 14.26.28720.3... 100%
Progress: Downloading KB3033929 1.0.5... 100%
Progress: Downloading KB3033929 1.0.5... 100%
Progress: Downloading chocolatey-windowsupdate.extension 1.0.4... 100%
Progress: Downloading chocolatey-windowsupdate.extension 1.0.4... 100%
Progress: Downloading KB3035131 1.0.3... 100%
Progress: Downloading KB3035131 1.0.3... 100%
Progress: Downloading KB2919355 1.0.20160915... 100%
Progress: Downloading KB2919355 1.0.20160915... 100%
Progress: Downloading KB2919442 1.0.20160915... 100%
Progress: Downloading KB2919442 1.0.20160915... 100%
Progress: Downloading KB2999226 1.0.20181019... 100%
Progress: Downloading KB2999226 1.0.20181019... 100%
Progress: Downloading python 3.8.3... 100%
Progress: Downloading python 3.8.3... 100%
 
chocolatey-core.extension v1.3.5.1 [Approved]
chocolatey-core.extension package files upgrade completed. Performing other installation steps.
 Installed/updated chocolatey-core extensions.
 The upgrade of chocolatey-core.extension was successful.
  Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-core'
 
chocolatey-windowsupdate.extension v1.0.4 [Approved]
chocolatey-windowsupdate.extension package files upgrade completed. Performing other installation steps.
 Installed/updated chocolatey-windowsupdate extensions.
 The upgrade of chocolatey-windowsupdate.extension was successful.
  Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-windowsupdate'
 
KB3035131 v1.0.3 [Approved]
kb3035131 package files upgrade completed. Performing other installation steps.
Skipping installation because update KB3035131 does not apply to this operating system (Microsoft Windows 10 Famille).
 The upgrade of kb3035131 was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
KB3033929 v1.0.5 [Approved]
kb3033929 package files upgrade completed. Performing other installation steps.
Skipping installation because update KB3033929 does not apply to this operating system (Microsoft Windows 10 Famille).
 The upgrade of kb3033929 was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
KB2919442 v1.0.20160915 [Approved]
kb2919442 package files upgrade completed. Performing other installation steps.
Skipping installation because this hotfix only applies to Windows 8.1 and Windows Server 2012 R2.
 The upgrade of kb2919442 was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
KB2919355 v1.0.20160915 [Approved]
kb2919355 package files upgrade completed. Performing other installation steps.
Skipping installation because this hotfix only applies to Windows 8.1 and Windows Server 2012 R2.
 The upgrade of kb2919355 was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
KB2999226 v1.0.20181019 [Approved]
kb2999226 package files upgrade completed. Performing other installation steps.
Skipping installation because update KB2999226 does not apply to this operating system (Microsoft Windows 10 Famille).
 The upgrade of kb2999226 was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
vcredist140 v14.26.28720.3 [Approved]
vcredist140 package files upgrade completed. Performing other installation steps.
Downloading vcredist140-x86
  from 'https://download.visualstudio.microsoft.com/download/pr/d60aa805-26e9-47df-b4e3-cd6fcc392333/A06AAC66734A618AB33C1522920654DDFC44FC13CAFAA0F0AB85B199C3D51DC0/VC_redist.x86.exe'
Progress: 100% - Completed download of C:\Users\haddo\AppData\Local\Temp\chocolatey\vcredist140\14.26.28720.3\VC_redist.x86.exe (13.75 MB).
Download of VC_redist.x86.exe (13.75 MB) completed.
Hashes match.
Installing vcredist140-x86...
vcredist140-x86 has been installed.
Downloading vcredist140-x64 64 bit
  from 'https://download.visualstudio.microsoft.com/download/pr/d60aa805-26e9-47df-b4e3-cd6fcc392333/7D7105C52FCD6766BEEE1AE162AA81E278686122C1E44890712326634D0B055E/VC_redist.x64.exe'
Progress: 100% - Completed download of C:\Users\haddo\AppData\Local\Temp\chocolatey\vcredist140\14.26.28720.3\VC_redist.x64.exe (14.28 MB).
Download of VC_redist.x64.exe (14.28 MB) completed.
Hashes match.
Installing vcredist140-x64...
vcredist140-x64 has been installed.
  vcredist140 may be able to be automatically uninstalled.
 The upgrade of vcredist140 was successful.
  Software installed as 'exe', install location is likely default.
 
vcredist2015 v14.0.24215.20170201 [Approved]
vcredist2015 package files upgrade completed. Performing other installation steps.
 The upgrade of vcredist2015 was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
python3 v3.8.3 [Approved]
python3 package files upgrade completed. Performing other installation steps.
Installing 64-bit python3...
python3 has been installed.
WARNING: Provided python InstallDir was ignored by the python installer
WARNING: Its probable that you had pre-existing python installation
WARNING: Installed to: C:\Users\haddo\AppData\Local\Microsoft\WindowsApps
WARNING: Installation folder is not the default. Not changing permissions. Please ensure your installation is secure.
  python3 can be automatically uninstalled.
Environment Vars (like PATH) have changed. Close/reopen your shell to
 see the changes (or in powershell/cmd.exe just type `refreshenv`).
 The upgrade of python3 was successful.
  Software installed as 'exe', install location is likely default.
 
python v3.8.3 [Approved]
python package files upgrade completed. Performing other installation steps.
 The upgrade of python was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
visualstudio2017-workload-vctools is not installed. Installing...
Progress: Downloading chocolatey-visualstudio.extension 1.8.1... 100%
Progress: Downloading chocolatey-visualstudio.extension 1.8.1... 100%
Progress: Downloading chocolatey-visualstudio.extension 1.8.1... 100%
Progress: Downloading visualstudio2017-workload-vctools 1.3.2... 100%
Progress: Downloading visualstudio2017-workload-vctools 1.3.2... 100%
Progress: Downloading visualstudio2017-workload-vctools 1.3.2... 100%
Progress: Downloading visualstudio-installer 2.0.1... 100%
Progress: Downloading visualstudio-installer 2.0.1... 100%
Progress: Downloading visualstudio-installer 2.0.1... 100%
Progress: Downloading visualstudio2017buildtools 15.9.23.0... 100%
Progress: Downloading visualstudio2017buildtools 15.9.23.0... 100%
Progress: Downloading visualstudio2017buildtools 15.9.23.0... 100%
Progress: Downloading dotnetfx 4.8.0.20190930... 100%
Progress: Downloading dotnetfx 4.8.0.20190930... 100%
Progress: Downloading dotnetfx 4.8.0.20190930... 100%
Progress: Downloading chocolatey-dotnetfx.extension 1.0.1... 100%
Progress: Downloading chocolatey-dotnetfx.extension 1.0.1... 100%
Progress: Downloading chocolatey-dotnetfx.extension 1.0.1... 100%
 
chocolatey-visualstudio.extension v1.8.1 [Approved]
chocolatey-visualstudio.extension package files upgrade completed. Performing other installation steps.
 Installed/updated chocolatey-visualstudio extensions.
 The upgrade of chocolatey-visualstudio.extension was successful.
  Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-visualstudio'
 
visualstudio-installer v2.0.1 [Approved]
visualstudio-installer package files upgrade completed. Performing other installation steps.
 The upgrade of visualstudio-installer was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
chocolatey-dotnetfx.extension v1.0.1 [Approved]
chocolatey-dotnetfx.extension package files upgrade completed. Performing other installation steps.
 Installed/updated chocolatey-dotnetfx extensions.
 The upgrade of chocolatey-dotnetfx.extension was successful.
  Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-dotnetfx'
 
dotnetfx v4.8.0.20190930 [Approved]
dotnetfx package files upgrade completed. Performing other installation steps.
Microsoft .NET Framework 4.8 or later is already installed.
 The upgrade of dotnetfx was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
visualstudio2017buildtools v15.9.23.0 [Approved]
visualstudio2017buildtools package files upgrade completed. Performing other installation steps.
Downloading channel manifest
  from 'https://aka.ms/vs/15/release/channel'
Progress: 100% - Completed download of C:\Users\haddo\AppData\Local\Temp\chocolatey\chocolatey-visualstudio.extension\ChannelManifest_81725945.man (69.48 KB).
Download of ChannelManifest_81725945.man (69.48 KB) completed.
Downloading catalog manifest
  from 'https://download.visualstudio.microsoft.com/download/pr/d0eac510-174b-4241-b73b-93dc7cc1fbf7/758680da6313838157f95e834155153d9c18088dfe7cbf894dfd3884bd9b5173/VisualStudio.vsman'
Progress: 100% - Completed download of C:\Users\haddo\AppData\Local\Temp\chocolatey\chocolatey-visualstudio.extension\Catalog_710991109.man (7.93 MB).
Download of Catalog_710991109.man (7.93 MB) completed.
Downloading visualstudio2017buildtools
  from 'https://download.visualstudio.microsoft.com/download/pr/d0eac510-174b-4241-b73b-93dc7cc1fbf7/9822b4c851e14d9658babd1533f66f518c6169196e985fe5713b2774128832ae/vs_BuildTools.exe'
Progress: 100% - Completed download of C:\Users\haddo\AppData\Local\Temp\chocolatey\visualstudio2017buildtools\15.9.23.0\vs_BuildTools.exe (1.2 MB).
Download of vs_BuildTools.exe (1.2 MB) completed.
Hashes match.
Installing visualstudio2017buildtools...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1028\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\2052\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1055\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1046\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1042\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1029\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1036\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\3082\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1040\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1031\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1045\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1041\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1049\help.html...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\HelpFile\1033\help.html...
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\vs_setup_bootstrapper.exe...
 
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.Diagnostics.Tracing.EventSource.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.VisualStudio.RemoteControl.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.VisualStudio.Setup.Common.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.VisualStudio.Setup.Configuration.Interop.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.VisualStudio.Setup.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.VisualStudio.Setup.Download.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.VisualStudio.Setup.Engine.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.VisualStudio.Telemetry.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Microsoft.VisualStudio.Utilities.Internal.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\Newtonsoft.Json.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\zh-Hans\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\zh-Hant\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\cs\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\es\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\pt-BR\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\tr\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\de\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\fr\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\it\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\pl\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\ko\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\ja\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\ru\vs_setup_bootstrapper.resources.dll...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\vs_setup_bootstrapper.config...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\vs_setup_bootstrapper.exe.config...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\detection.json...
 
Preparing: C:\Users\haddo\AppData\Local\Temp\chocolatey\45f97e1e9be68bd8b6334aaaa8c1\vs_bootstrapper_d15\vs_setup_bootstrapper.json...
 
visualstudio2017buildtools has been installed.
  visualstudio2017buildtools may be able to be automatically uninstalled.
 The upgrade of visualstudio2017buildtools was successful.
  Software installed to '"C:\Program Files (x86)\Microsoft Visual Studio\Installer"'
 
visualstudio2017-workload-vctools v1.3.2 [Approved]
visualstudio2017-workload-vctools package files upgrade completed. Performing other installation steps.
Installing visualstudio2017-workload-vctools...
 
visualstudio2017-workload-vctools has been installed.
  visualstudio2017-workload-vctools may be able to be automatically uninstalled.
 The upgrade of visualstudio2017-workload-vctools was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.
 
Chocolatey upgraded 17/17 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
 
Upgraded:
 - visualstudio2017buildtools v15.9.23.0
 - python v3.8.3
 - kb2919355 v1.0.20160915
 - kb3033929 v1.0.5
 - kb2999226 v1.0.20181019
 - chocolatey-core.extension v1.3.5.1
 - python3 v3.8.3
 - dotnetfx v4.8.0.20190930
 - chocolatey-visualstudio.extension v1.8.1
 - vcredist2015 v14.0.24215.20170201
 - visualstudio2017-workload-vctools v1.3.2
 - kb2919442 v1.0.20160915
 - visualstudio-installer v2.0.1
 - vcredist140 v14.26.28720.3
 - chocolatey-dotnetfx.extension v1.0.1
 - kb3035131 v1.0.3
 - chocolatey-windowsupdate.extension v1.0.4
 
Packages requiring reboot:
 - vcredist140 (exit code 3010)
 
The recent package changes indicate a reboot is necessary.
 Please reboot at your earliest convenience.
Type ENTER to exit:

Y a ça qui me chiffone un peu:
Pièce jointe 569336

Bonjour,

Apparemment il manque des dépendances a Jquery pour l'instal de boostrap.

Comment on fait ça ?

En revanche pour sass, j'ai peut-etre trouver la solution car j'ai installé koala: http://koala-app.com/

Code:

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
PS C:\Users\haddo> cd /
PS C:\> cd Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom> npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sensible defaults.
 
See `npm help json` for definitive documentation on these fields
and exactly what they do.
 
Use `npm install <pkg>` afterwards to install a package and
save it as a dependency in the package.json file.
 
Press ^C at any time to quit.
package name: (projet-bootstrap-openclassroom)
version: (1.0.0)
description: oopenclassroom
entry point: (index.js)
test command:
git repository:
keywords:
author:
license: (ISC)
About to write to C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom\package.json:
 
{
  "name": "projet-bootstrap-openclassroom",
  "version": "1.0.0",
  "description": "oopenclassroom",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}
 
 
Is this OK? (yes)
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom> npm install --save bootstrap
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN bootstrap@4.5.0 requires a peer of jquery@1.9.1 - 3 but none is installed. You must install peer dependencies yourself.
npm WARN bootstrap@4.5.0 requires a peer of popper.js@^1.16.0 but none is installed. You must install peer dependencies yourself.
npm WARN projet-bootstrap-openclassroom@1.0.0 No repository field.
 
+ bootstrap@4.5.0
added 1 package from 2 contributors and audited 1 package in 1.75s
 
1 package is looking for funding
  run `npm fund` for details
 
found 0 vulnerabilities
 
PS C:\Users\haddo\Documents\CODEUR\Projet-bootstrap-openclassroom>

25/02/2022, 12h08
yanDimitri

A la réponse sass n'est pas reconnu comme nom d'applet, etc...

Bonjour à tous.

:lol:J'ai cherché de mon coté après avoir eu le même problème. La réponse est assez simple en fait et même déroutante , il suffit d'installer "sass" de manière générale.
"npm install -g sass":ccool:
J'espère que cela marchera de votre coté, merci à vous.