Dylan N

with @brunolemos PR, will we still have "create-react-app-typescript" support react-scripts@next (webpack4) ?

will it work if we add a parameter like "errorCode=400" to the URL to simulate it like: curl http://localhost:3003/todos?errorCode=400 @ltbaogt2

@alvaromb: could you merge this minor commit? Thanks.

@alvaromb The failed tests may be related to this - https://github.com/facebook/jest/issues/1840 Have you tried this? > This was due react@^15.3.2 resolve to [email protected] due how npm semver works. > Setting...

Hi, it works for me with Node 15.5.0. Did you have MongoDB started first? ``` $ node -v v15.5.0 $ yarn dev yarn run v1.22.5 $ npx nodemon --watch 'src/**/*.ts'...

@bubonicfred @chmac Thanks for reaching out! Yes, we should have the same spec, something that users are already familiar with other systems. Just like icons, users don't have to re-learn...

can't wait to have this great UI kit upgraded with tailwind v3, I forked it here: https://github.com/ngduc/windmill-react-ui-kit upgraded and fixed a few things for storybook also.

I tried truffle-flattener but it failed. For this issue, copy the openzepplin's "contracts" directory to ./node_modules/.bin/poa-solidity-flattener then it should work. your contract should look use import with relative path like...

@8483 have you tried this example? https://github.com/ngduc/react-tabulator/blob/master/src/ReactTabulatorExample.tsx#L22

@8483 I will look into this to see any alternative to ReactDOM.render If anyone can help, it'll be great.