These are chat archives for reactioncommerce/reaction

30th
Jan 2019
Kamelia2000
@Kamelia2000
Jan 30 07:45
I have just a question why the solution is very slow
Kamelia2000
@Kamelia2000
Jan 30 07:57
The site launched by reactioncommerce is too slow
Michael Dekker
@firstred
Jan 30 07:57
@Kamelia2000 Why do you keep posting in every ecommerce chat that the solution is slow?
It got you banned from the PrestaShop one
Kamelia2000
@Kamelia2000
Jan 30 07:57
Because i am looking for best
I dont want to judge
You can just check and see by youself .We would like to choose best one .
prestashop is terrible
Michael Dekker
@firstred
Jan 30 07:58
lol
What exactly are you looking for?
Kamelia2000
@Kamelia2000
Jan 30 07:59
Let me share you a web site build by Reactioncommerce
Just check by yourself
Michael Dekker
@firstred
Jan 30 07:59
AFAIK Reaction Commerce 2.0.0 has some decent tech that could make it the fastest one out there
meteor.js didn't look like the right option, the "reactivity" is a real burden on its performance
though you can still achieve decent page load times w/ 1.xx
Kamelia2000
@Kamelia2000
Jan 30 08:01
@firstred Honestly the mind behind Reactioncommerce is great just performanceh ave big problem . But prestashop from base is Terrible.Its a Monolitic solution with old Architecture
Michael Dekker
@firstred
Jan 30 08:01
but the developer experience with 1.xx is more like waiting than actual coding in my experience, setting METEOR_DISABLE_OPTIMISTIC_CACHING=1 helps a bit
Yeah, I have been coding for both, PrestaShop 1.7 is getting harder and harder with every minor version
due to it not only being monolithic, but merging both Symfony and legacy code into pieces that no one understands
not really my favorite kind of architecture
Reaction Commerce 2.0.0 kind of is
I have used a comparable stack before and could really achieve some great performance with it
developer experience w/ next.js was awesome imo
I would recommend to start with next.js first, get a feeling of how you can build sites with React
Michael Dekker
@firstred
Jan 30 08:09
then move on to the ecomm part w/ Reaction Commerce
Abhishek
@thegtagamer
Jan 30 11:13

@loan-laux so what is happening is the meteor browser policy is converting this URL "https://tagmanager.google.com/debug/debuguiApp.js"
to this
"https://tagmanager.google.com/debug/debuguiapp.js"

and ergo since the debuguiapp.js doesnt exists... it is unable to load so

I guess the meteor guys are doing some sorta camel-case conversion of script URL's to lowercase in BrowserPolicy Package
Abhishek
@thegtagamer
Jan 30 11:20
Does anyone know how to prevent this conversion from happening ?
Patrick Newell
@pnewell4_twitter
Jan 30 11:25
@thegtagamer in the short term, can you use a wildcard?
BrowserPolicy.content.allowOriginForAll("https://tagmanager.google.com/*");
Abhishek
@thegtagamer
Jan 30 11:25
@pnewell4_twitter sure
I tried that
it doesnt seems to work
import { BrowserPolicy } from "meteor/browser-policy-common";

BrowserPolicy.content.allowOriginForAll("https://stats.g.doubleclick.net/r/collect*");
BrowserPolicy.content.allowOriginForAll("https://www.google.com/ads/*");
BrowserPolicy.content.allowOriginForAll("https://www.google.co.in/ads/*");
BrowserPolicy.content.allowImageOrigin("google.com/ads/ga-audiences");
BrowserPolicy.content.allowImageOrigin("google.co.in/ads/ga-audiences");
BrowserPolicy.content.allowOriginForAll("https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js");
BrowserPolicy.content.allowOriginForAll("https://cdn.rawgit.com/prashantchaudhary/ddslick/master/jquery.ddslick.min.js");
BrowserPolicy.content.allowOriginForAll("tagmanager.google.com/*");
BrowserPolicy.content.allowInlineScripts("tagmanager.google.com/*");
BrowserPolicy.content.allowEval("tagmanager.google.com/*");
BrowserPolicy.content.allowStyleOrigin("tagmanager.google.com/*");
BrowserPolicy.content.allowInlineStyles("tagmanager.google.com/*");

BrowserPolicy.content.allowOriginForAll("tagmanager.google.com/debug/*");
BrowserPolicy.content.allowInlineScripts("tagmanager.google.com/debug/*");
BrowserPolicy.content.allowEval("tagmanager.google.com/debug/*");
BrowserPolicy.content.allowStyleOrigin("tagmanager.google.com/debug/*");
BrowserPolicy.content.allowInlineStyles("tagmanager.google.com/debug/*");

BrowserPolicy.content.allowOriginForAll("tagmanager.google.com/debug");
BrowserPolicy.content.allowInlineScripts("tagmanager.google.com/debug");
BrowserPolicy.content.allowEval("tagmanager.google.com/debug");
BrowserPolicy.content.allowStyleOrigin("tagmanager.google.com/debug");
BrowserPolicy.content.allowInlineStyles("tagmanager.google.com/debug");


BrowserPolicy.content.allowOriginForAll("https://tagmanager.google.com/debug/css.css");
BrowserPolicy.content.allowInlineScripts("https://tagmanager.google.com/debug/css.css");
BrowserPolicy.content.allowEval("https://tagmanager.google.com/debug/css.css");
BrowserPolicy.content.allowStyleOrigin("https://tagmanager.google.com/debug/css.css");
BrowserPolicy.content.allowInlineStyles("https://tagmanager.google.com/debug/css.css");


BrowserPolicy.content.allowOriginForAll("https://tagmanager.google.com/debug/angular-bundle.js");
BrowserPolicy.content.allowInlineScripts("https://tagmanager.google.com/debug/angular-bundle.js");
BrowserPolicy.content.allowEval("https://tagmanager.google.com/debug/angular-bundle.js");
BrowserPolicy.content.allowStyleOrigin("https://tagmanager.google.com/debug/angular-bundle.js");
BrowserPolicy.content.allowInlineStyles("https://tagmanager.google.com/debug/angular-bundle.js");

BrowserPolicy.content.allowOriginForAll("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");
BrowserPolicy.content.allowInlineScripts("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");
BrowserPolicy.content.allowEval("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");
BrowserPolicy.content.allowStyleOrigin("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");
BrowserPolicy.content.allowInlineStyles("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");
BrowserPolicy.content.allowImageOrigin("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");
BrowserPolicy.content.allowMediaOrigin("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");
BrowserPolicy.content.allowFontOrigin("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");
BrowserPolicy.content.allowScriptOrigin("https://ssl.gstatic.com/analytics-suite/header/legacy/v2/ic_tag_manager.svg");



BrowserPolicy.content.allowOriginForAll("https://www.gstatic.com/images/icons/material/system/1x/keyboard_arrow_up_white_48dp.png");
BrowserPolicy.content.allowInlineScripts("https://www.gstatic.com/images/icons/material/system/1x/keyboard_arrow_up_white_48dp.png");
Patrick Newell
@pnewell4_twitter
Jan 30 11:29

oh. :frowning:
I have moved into the 2.0 world, but for my 1.0 install, I used this:

BrowserPolicy.content.allowOriginForAll("www.google-analytics.com");

not the safest, but it worked

Abhishek
@thegtagamer
Jan 30 11:30
lemme try this too
@pnewell4_twitter hey patrick, just for info..If we use the react package for gtm..do we still face the CSP issues with them too ?
Patrick Newell
@pnewell4_twitter
Jan 30 11:33
probably?
I imagine the logging that package does would still need to be allowed
Lebzanwa
@Lebzanwa
Jan 30 21:28
$ reaction
INFO: Could not find files for the given pattern(s).
Setting up plugin imports...

Setting up style imports...

Provisioning assets...

[[[[[ ~\F\yshop\reaction ]]]]]

=> Started proxy.
=> A patch (Meteor 1.8.0.2) for your current release is available!
   Update this project now with 'meteor update --patch'.
=> Started MongoDB.


#
# Fatal error in , line 0
# API fatal error handler returned after process out of memory
#
{ Error: Command failed: meteor --raw-logs
    at checkExecSyncError (child_process.js:622:11)
    at execSync (child_process.js:659:13)
    at _callee$ (C:\Users\Lebogang Nkhuna\AppData\Roaming\npm\node_modules\reaction-cli\dist\commands\run.js:72:43)
    at tryCatch (C:\Users\Lebogang Nkhuna\AppData\Roaming\npm\node_modules\reaction-cli\node_modules\regenerator-runtime\runtime.js:65:40)
    at Generator.invoke [as _invoke] (C:\Users\Lebogang Nkhuna\AppData\Roaming\npm\node_modules\reaction-cli\node_modules\regenerator-runtime\runtime.js:303:22)
    at Generator.prototype.(anonymous function) [as next] (C:\Users\Lebogang Nkhuna\AppData\Roaming\npm\node_modules\reaction-cli\node_modules\regenerator-runtime\runtime.js:117:21)
    at step (C:\Users\Lebogang Nkhuna\AppData\Roaming\npm\node_modules\reaction-cli\dist\commands\run.js:98:191)
    at C:\Users\Lebogang Nkhuna\AppData\Roaming\npm\node_modules\reaction-cli\dist\commands\run.js:98:361
    at process.internalTickCallback (internal/process/next_tick.js:77:7)
  status: 3221225477,
  signal: null,
  output: [ null, null, null ],
  pid: 1400,
  stdout: null,
  stderr: null }

Error: App failed to start
I'm trying to run the app. Please advice..