DEV Community

Discussion on: Deno is coming

Collapse
 
bsodmike profile image
Michael de Silva • Edited

It sounds like deno is going to be npm incompatible (just by its name!); not sure if yarn would support it. So my larger question, what would be the options for deno in terms of:

  • Managing package dependencies
  • Managing the version of deno installed (on your dev system)
  • deno & webpack, how would this work?

I also hope folks picked up on the fact that deno is node switched around 😏

Thanks!

Collapse
 
jcs224 profile image
Joe Sweeney

Well, if you want to see a resource for ES6 import-compatible libraries (compatible with Deno), Pika looks like the best option right now.

Collapse
 
omenlog profile image
Omar E. Lopez

I think that we won't need some dependencies management basing in the fact that they are defined at the import statements using urls, which serves to identify them.

As deno has a bundler out of the box the intention should be that developers use this bundler and not third party options (Webpack, Parcel, Rollup), the same principle can by applied for testing , linting and formatting

Good question about different versions in the system, but the platform is shipped as a single executable so isn't hard build some tool like nvm

Thanks for your comment