
                    For edge, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

I was able to fix this by manually creating the directory before running serverless with: mkdir -p /root/.serverless/components/registry/npm/@sls-next/serverless-component@1.17.0

serverless next.js serverless remove Error: Cannot find module '/root/.serverless/components/registry/npm/@sls-next/serverless-component@1.18.0-alpha.18/node_modules/@sls-next/serverless-component'

Great success! Pasting code here for others. What problem are you trying to solve?
With the new updates to v8 

metamask extension Allow dapp to disconnect accounts

Hi folks please pin the version number in your serverless.yml like it states in the README For example: 

serverless next.js Started getting the Error: Cannot find module '@sls-next/next-aws-cloudfront'

To understand this problem it's important to understand the difference between gasPrice and gasLimit Gas price is your bid (in ether) per unit of gas 

metamask extension etimateGas failing 9/10 times when it should succeed

Ahh you had keep: False so it would have deleted the file at the end of the state anyway But I figured it out 

salt archive.extracted ValueError "No path specified" in 2017.7.3

Same for 10.2.3 Using webpack 5 returns the following from Cloudfront:


Using versions: 

serverless next.js Using webpack 5 causes 503

You need to make sure you specify both networkId and chainId and they are the same values 

metamask extension Newer version of matamask throws errors when sending transaction.

I was also facing the same issue (getting Error: Source and destination must not be the same) and spent some time to debug what's happening 

serverless next.js Error: Source and destination must not be the same. When using useServerlessTraceTarget

Had a similar problem this is perhaps better solved by editing your wide github userstyle and adding style like this:


The problem is 

octotree Not compatible with GitHub Wide plugin

I'm having this same issue with 2018.3.0 My salt-minion is also on 2018.3.0 This is what I'm getting in /var/log/salt/master: 

salt 2017.7.4 to 2018.3.0 upgrade issue: Salt request timed out. The master is not responding

Here is my fix
/usr/lib/python2.7/site-packages/salt/log/mixins.py


The following needs to be implemented on every function not just trace 

salt salt logging with plain str (ascii) with unicode chars causes UnicodeDecodeError PY2

It should be fixed now in@sls-next/serverless-component@1.19.0-alpha.19 after also include 7256ab9 Will try to optimize/bundle this better in the future 