Webpack dat-dns not found
See original GitHub issueWhen using the dat-sdk as described in the README with Webpack/Vue it does have an issue loading dat-dns
:
const SDKPromise = require('dat-sdk/promise')
Error message:
* dns in ./node_modules/node-dat-archive/node_modules/dat-dns/index.js
The sample, see App.vue
for the problematic import:
datbox.zip
Issue Analytics
- State:
- Created 4 years ago
- Comments:20 (14 by maintainers)
Top Results From Across the Web
Missing Net and Dns dependencies in webpack #748 - GitHub
joi/lib/string.js Module not found: Error: Cannot resolve module 'net' in /Users/. ... Missing Net and Dns dependencies in webpack #748.
Read more >webpack-dev-server: command not found - Stack Overflow
I found the accepted answer does not work in all scenarios. ... webpack-dev-server in the command line re-installed the missing folder and fixed...
Read more >webpack-dev-server: command not found error [Solved]
To solve the error "webpack-dev-server: command not found", install the package globally by running npm install -g webpack-dev-server and restart your terminal.
Read more >dat-sdk - npm
Dat consists of a bunch of low level building blocks for working with data in ... To bundle with webpack, you'll need to...
Read more >Dat Consortium Meeting 35 - HackMD
Updates; Manifesto updates (Martin); OC Migration Results (Mauve); DAT-DNS in beaker/agregore (Martin); Documenting all things Dat Ecosystem ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ha ha, okay I think I got it, it’s an SDK bug after all. 😛 Not sure why it isn’t manifesting with browserify. I’ll ping you when I have a fix out.
This should be fixed if you use the config in #43
Big thanks to @urgent for figuring this out!