You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all our NodeJS Commons packages are NodeJS-native. However, it makes more sense to make packages that are runtime-independent (like universal for example) to be Deno-native and use dnt to generate their NPM versions. Deno packages are easier to manage and test but NPM is more universally accessible.
For packages like nlc-astro and nlc-remark it probably makes sense to leave them as NodeJS-native but nlc-universal will probably be best as Deno-native. We'll need to make case-by-case decisions based on whether a library has any value outside of NodeJS (e.g. for Bun or Deno).
The text was updated successfully, but these errors were encountered:
Currently all our NodeJS Commons packages are NodeJS-native. However, it makes more sense to make packages that are runtime-independent (like
universal
for example) to be Deno-native and usednt
to generate their NPM versions. Deno packages are easier to manage and test but NPM is more universally accessible.For packages like
nlc-astro
andnlc-remark
it probably makes sense to leave them as NodeJS-native butnlc-universal
will probably be best as Deno-native. We'll need to make case-by-case decisions based on whether a library has any value outside of NodeJS (e.g. for Bun or Deno).The text was updated successfully, but these errors were encountered: