We moved from dll hell to install hell...This is what keeps me from engaging in SharePoint development (and I have done a lot wsp development in the past)
You can install all dependencies to your dev machine with single command and you are good to go. Not sure where the "hell" term comes with that and it's aligned on the industry standard web stack development patterns. If you have any issues with the required steps, please submit an issue at aka.ms/spfx-issues and we can help.
I ran into a few issues , error at gulp serve, when I created solution. >gulp trust-dev-cert node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module 'C:\Users\u8035awe\AppData\Roaming pm ode_modules\gulp\bin\gulp.js' ←[90m at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m ←[90m at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)←[39m ←[90m at node:internal/main/run_main_module:17:47←[39m { code: ←[32m'MODULE_NOT_FOUND'←[39m, requireStack: [] } Note: It worked with me befor then I started running with error like funding , version , I started uninstalling and installing but no luck . Today I managed to get to this stage. node 16 installed
This is a bit confusion from our side - you will need to execute the 'gulp trust-dev-cert' command in a project - so it only works AFTER you have scaffolded a SPFx solution and you execute that in that folder... even though the command is global and not solution/project specific. Hopefully that gets you unblocked.
@@MicrosoftCommunityLearning thanks for your reply. I did execute command after I created solution and we part type . I did go through this procedure and created a web part on my sharepoint site 2 months ago then I ran into issues then from that date I still facing errors. I tried fresh installation but no luck.
@@MrAbueslam Can you post this question at the aka.ms/spfx-issues as we have engineers and other community members helping there around these kind of situations. Just easier to get help from that channel with multiple people helping questions.
That's absolutely an option and works great as well. We are not really defining the "recommended" option as what works for one, might not be good for another. These videos provide baseline but can be of course extended with the NVM usage.
I'm getting the following error installing Chocolatey Exception calling "DownloadString" with "1" argument(s): "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." Any suggestions?
So much of Microsoft's bot framework and other tools are out of date, even in this 10 month old video, they talk about being too far behind to use the latest version.... I had so many dependency issues while trying to install your prerequisites on windows. Wasted days of time before even getting to write a single line of code!
We'd love to hear more on what kind of problems you had and where we can improve - any change you could provide an issue at aka.ms/spfx-issues for us to track this. Thx.
I use node.js 14.16.1 for SPFX environment. When I ran: npm install -g yo@4.2.0, keep getting self sign cert chain error even though I have already set this in .npmrc file. also run them in command line, strict-ssl=false ca= NODE_TSL_REJECT_UNAUTHORIZED=0 still in vain I ran npm from /users/id/ directory
Thank you! And it was raining there. ^^'
We moved from dll hell to install hell...This is what keeps me from engaging in SharePoint development (and I have done a lot wsp development in the past)
You can install all dependencies to your dev machine with single command and you are good to go. Not sure where the "hell" term comes with that and it's aligned on the industry standard web stack development patterns.
If you have any issues with the required steps, please submit an issue at aka.ms/spfx-issues and we can help.
@@MicrosoftCommunityLearning Nothing Microsoft tells you to do works.
while trying to execute the npm I'm facing run 'nom fund' for details can't able to install, any idea how to fix this.
Ahh the good old times when I could just install a vm with everything..
uh why good old times , its only been a year
very very useful, thank you!
@10:28 your cli doesn't show depreciated. I think your background color is the same as the text. (First line after install gulp-cli)
I ran into a few issues , error at gulp serve, when I created solution.
>gulp trust-dev-cert
node:internal/modules/cjs/loader:936
throw err;
^
Error: Cannot find module 'C:\Users\u8035awe\AppData\Roaming
pm
ode_modules\gulp\bin\gulp.js'
←[90m at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)←[39m
←[90m at node:internal/main/run_main_module:17:47←[39m {
code: ←[32m'MODULE_NOT_FOUND'←[39m,
requireStack: []
}
Note: It worked with me befor then I started running with error like funding , version , I started uninstalling and installing but no luck . Today I managed to get to this stage.
node 16 installed
This is a bit confusion from our side - you will need to execute the 'gulp trust-dev-cert' command in a project - so it only works AFTER you have scaffolded a SPFx solution and you execute that in that folder... even though the command is global and not solution/project specific. Hopefully that gets you unblocked.
@@MicrosoftCommunityLearning thanks for your reply. I did execute command after I created solution and we part type . I did go through this procedure and created a web part on my sharepoint site 2 months ago then I ran into issues then from that date I still facing errors. I tried fresh installation but no luck.
@@MrAbueslam Can you post this question at the aka.ms/spfx-issues as we have engineers and other community members helping there around these kind of situations. Just easier to get help from that channel with multiple people helping questions.
Thank you
Nice one Vesa. Is NVM is not a recommended way? To install node
That's absolutely an option and works great as well. We are not really defining the "recommended" option as what works for one, might not be good for another. These videos provide baseline but can be of course extended with the NVM usage.
You would think Microsoft would give him a better microphone.
I'm getting the following error installing Chocolatey
Exception calling "DownloadString" with "1" argument(s): "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."
Any suggestions?
Please report any issue at aka.ms/spfx-issues. We have SPFx engineering team helping with the questions there.
Is your time/date set correctly?
There has to be an easier way. I had a tough time with the installation. Wasn't as smooth as you have shown
Please share your issues at aka.ms/spfx-issues, so that we know what was wrong. Thx.
So much of Microsoft's bot framework and other tools are out of date, even in this 10 month old video, they talk about being too far behind to use the latest version.... I had so many dependency issues while trying to install your prerequisites on windows. Wasted days of time before even getting to write a single line of code!
We'd love to hear more on what kind of problems you had and where we can improve - any change you could provide an issue at aka.ms/spfx-issues for us to track this. Thx.
Can you show the set up process on an M1 Mac, I'm getting a lot of errors
Can you please share details on the issues you are seeing at aka.ms/spfx-issues and our engineering team can help to get things sorted out. Thx.
gulp trust-dev-cert command shows error for generating the certificate
Please submit details at aka.ms/spfx-issues and we'll have engineering helping you to get unblocked.
I use node.js 14.16.1 for SPFX environment.
When I ran: npm install -g yo@4.2.0, keep getting self sign cert chain error
even though I have already set this in .npmrc file.
also run them in command line, strict-ssl=false ca= NODE_TSL_REJECT_UNAUTHORIZED=0
still in vain
I ran npm from /users/id/ directory