Subodh Pareek
Subodh Pareek
Try adding this line to your custom webpack config instead of putting `NODE_PATH` in your scripts. ```js // backpack.config.js // https://webpack.js.org/configuration/resolve/#resolve-modules module.exports = { webpack: (config, options, webpack) => {...
What you can also do is make aliases, so as to not pollute the global namespace and keep things clear. ```js const path = require('path'); module.exports = { webpack: (config,...
Thank You!! 🎉 Minor Feedback, I'd go with a darker color in the top left where it says Insomnia
A monolith might be a good way to start, and the conventional feathers service definitely is service oriented and would make it super easy to pluck it out and put...
Facing the same issue while on flask. It's working fine when running on my local, but when deployed to AWS inside a docker container get an error. ``` Flask==0.10.1 rollbar~=0.15...
yes please 😢
@daffl `app.on('logout')` seems to not be generating for rest provider. `app.on('login')` seems to be generating for both socket io and rest
The above work around works well on initial load, but when I zoom in to the tree, the same issue persists
I was able to run this package by installing a plugin and making two changes in the `next.config.js` file. ```bash npm i -s next-transpile-modules ``` ```js // next.config.js const withTM...
Yes that's a good idea, but perhaps make it optional in the setting?