0

We are in process of developing a custom command set following this link and ended up in a road blocker as our organization is very strict on github usage. Downloading required components like phantom.js itself failed due to restrictions here and facing issues while setting up the dev environment.

My question, is there any other way to develop such extension without yeoman/gulp? Maybe a silly question but am having this challenge in my extended SP dev role in addition to my usual role.

Any pointer like articles or how-to may help me & others like me.

2
  • 2
    Not a silly question at all. Though, AFAIK, that is the only way(yeoman/gulp) to develop spfx solutions. I know a bit about corporate bureaucracy and its sometimes crazy restrictions, but would suggest you to ask your organization to "open up" these links for download as they are absolutely essential to develop any modern front-end web apps. Commented Apr 2, 2018 at 16:52
  • thanks @GautamSheth for your reply. this helps to justify the fact & expedite my team towards goal.. appreciate if you post this as answer, I can mark it. Commented Apr 2, 2018 at 17:22

1 Answer 1

1

The link posted by you in the question is the official MS suggested approach to develop SPFx extensions. They themselves use this approach to develop certain stuff.

It relies on yeoman/gulp and npm packages. While theoretically there might be a way to develop extensions, since it is all JavaScript on the inside, you might end up re-inventing the wheel and it would not be a supported way for the future.

So, would suggest that you work with your organization and whitelist certain links which would be necessary for you to develop SPFx solutions,

Not the answer you're looking for? Browse other questions tagged or ask your own question.