Skip to main content
Cardano

Return to Answer

attempted to make answer clearer to address bot comment. also give credit.
Source Link
TheStophe
TheStophe
  • 400
  • 1
  • 13

When starting the client server on macOS use GC_DONT_GC=1 npm run start.

That is, includinginclude GC_DONT_GC=1 worked in front of the beginning:command GC_DONT_GC=1 npm run start.

  • From new terminal tab in ~/plutus-apps directory,
  • start client cd plutus-playground-client and GC_DONT_GC=1 npm run start

Then, open a browser tab to httpshttp://localhost:8009/ and, using Brave Browser, Advance from warnings. (Not https, see note below).

Note: I had to click "Advance" from warningupdate my Plutus-apps/plutus-playground-client/webpack.config.js file per prodineeritecht's recommendation to bi-pass the https proxy firewall.

When starting the client server on macOS, including GC_DONT_GC=1 worked in the beginning: GC_DONT_GC=1 npm run start

  • From new terminal tab in ~/plutus-apps directory,
  • start client cd plutus-playground-client and GC_DONT_GC=1 npm run start

Then, open a browser tab to https://localhost:8009/ and, using Brave Browser, I had to click "Advance" from warning.

When starting the client server on macOS use GC_DONT_GC=1 npm run start.

That is, include GC_DONT_GC=1 in front of the command npm run start.

Then, open a browser tab to http://localhost:8009/ and, using Brave Browser, Advance from warnings. (Not https, see note below).

Note: I had to update my Plutus-apps/plutus-playground-client/webpack.config.js file per prodineeritecht's recommendation to bi-pass the https proxy firewall.

Grammar and formatting
Source Link
gRebel
gRebel
  • 1.8k
  • 1
  • 9
  • 36

For whatever reason, whenWhen starting the client server on macOS, including GC_DONT_GC=1 worked in the beginning worked: GC_DONT_GC=1 npm run startGC_DONT_GC=1 npm run start

  • From new terminal tab in ~/plutus-apps directory,
  • start client cd plutus-playground-client and GC_DONT_GC=1 npm run start

Then, open a browser tab to https://localhost:8009/ and, using Brave Browser, I had to click "Advance" from warning.

For whatever reason, when starting the client server on macOS, including GC_DONT_GC=1 in the beginning worked: GC_DONT_GC=1 npm run start

  • From new terminal tab in ~/plutus-apps directory,
  • start client cd plutus-playground-client and GC_DONT_GC=1 npm run start

Then, open a browser tab to https://localhost:8009/ and, using Brave Browser, I had to click "Advance" from warning.

When starting the client server on macOS, including GC_DONT_GC=1 worked in the beginning: GC_DONT_GC=1 npm run start

  • From new terminal tab in ~/plutus-apps directory,
  • start client cd plutus-playground-client and GC_DONT_GC=1 npm run start

Then, open a browser tab to https://localhost:8009/ and, using Brave Browser, I had to click "Advance" from warning.

Source Link
TheStophe
TheStophe
  • 400
  • 1
  • 13

For whatever reason, when starting the client server on macOS, including GC_DONT_GC=1 in the beginning worked: GC_DONT_GC=1 npm run start

  • From new terminal tab in ~/plutus-apps directory,
  • start client cd plutus-playground-client and GC_DONT_GC=1 npm run start

Then, open a browser tab to https://localhost:8009/ and, using Brave Browser, I had to click "Advance" from warning.