-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
spack: meta issue #841
Comments
Hey, is spack on crates.io yet? (And on the side note, is there an actual crate that exposes |
@jakajancar Sorry for late response. Managing multi crate repository is a big pain if some of those are published... |
@jakajancar Bundler is now on crates.io |
@kdy1 Is there a recommended way to invoke |
@jrop You can use |
@kdy1 I was hoping to avoid a dependency on NodeJS |
It's possible, but I'm not sure if it worths. |
@ScottAwesome no, swc uses napi-rs |
I'll publish the initial version without doing tasks written here.
Tasks
type
app
- Bundles everything, just like webpacklib
- Preserve module requires, just like rollupWatch mode
Small fix for node_resolver (We need to include
.ts
by default)spack.config.ts
swc.bundle([conf1, conf2])
Handle dynamic import
Provide webpack-like plugin / loader /resolver api
This is really a show-stopper. I'm going to publish first version without support for plugins. This requires one of the below, as spack uses all cpu cores.
Promise API neon-bindings/neon#73
Can I await javascript promise from rust? infinyon/node-bindgen#37
Implement minifier (Minifier #826)
Conditional imports
Run global inlining pass for each module before analyzing dependencies.
The text was updated successfully, but these errors were encountered: