-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be a tsc
.
#20
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The point would be to make Deno code a first-class TypeScript complication source. If your project compiles, you can make it compatible with Deno and it'll still compile. |
One could re-use TypeScript's argv parser... |
That would indeed be pretty cool! I find feature parity with tsc a pretty compelling argument. It's amazing for complex projects that may rely on tsc a lot. It's also amazing for beginners because they're familiar with the interface of tsc so they can trust that the learning curve is flat. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Way too complex, I'm not interested in rolling my own scaffolding tool from scratch... |
...At least until |
Maybe we can think differently about handling the complexity. All of What is the minimal setup that would work for At the same time, |
Everything in https://github.com/fromdeno/template is useful to some degree:
|
Useful, not required. Drop.
Useful only on GitHub. Drop.
Useful only in git. Drop, but print message if in git which folders to ignore.
Useful only with this editor. Drop.
Generate. Values could be chosen dynamically. Do not store a static file.
No other tool defines entry points. Unexpected. Drop. Optionally, print link to getting started guide.
Change config. Not all projects need this. (Example: grammY runner.) Drop.
Tap into |
Weird middle ground. At that point, might as well create it.
#21 already modifies the |
|
Actually, I'll resurrect it today |
Reopening to keep track of the other ideas mentioned here |
I would love
deno2node
to behave exactly like atsc
that is Deno-aware. I see this as the main advantage overdnt
—instead of having some magic black box that somehow tries to do everything, it would be awesome to do just one thing, and do it really well: compiling Deno code for Node.That way, we could use our existing Node workflows that are based around
tsc
, and usedeno2node
as a drop-in replacement once we move to Deno. As a result, all existing infra and Node tooling will keep on working. I cannot imagine howdnt
is going to solve denoland/dnt#60 in the foreseeable future, butdeno2node
already integrates seamlessly with Node workflows.At the same time, it enables us to write Deno code most of the time. We can use all their tooling, hosting, docs, infra, and all other advantages. On the Node side, in contrast to
dnt
, we still remain in control of our own configs and setup. In a way,deno2node
brings the best of both worlds, because we can target both platforms natively, and use the familiar tooling of both ecosystems.Some points that would be amazing to see are the following.
deno2node --init
creates a clean project from scratch which targets both Deno and Node.deno2node
runs without a file path totsconfig.json
, and it behaves liketsc
would do without config file.deno2node
supports those compiler options that make sense from https://www.typescriptlang.org/docs/handbook/compiler-options.html#compiler-optionsThe text was updated successfully, but these errors were encountered: