Comments (3)
Heh, I had a feeling someone would request this. I've been trying to keep this project zero/low-configuration and focused on the "fast development builds" use case, but I suppose it's reasonable that people would want the same code running in dev and prod. FWIW, my use case at work is to only use it in development and still use Babel and tsc for prod builds, since we still want to support IE. Production builds are also already slower, and they run in CI anyway, so the speed gains from Sucrase are unimportant there.
Do you have thoughts on the right config here? Currently I'm thinking there can be a new production?: boolean
in the options, which will exclude __self
and __source
. In the future, if some other transform wants to behave differently in dev and prod, it can use that flag. If there's a real use case for configuring the transforms individually, then that can be done with new options, but I'd prefer to keep the config small.
Happy to accept a PR (using the production
flag above), or I can try implementing it when I get a chance.
from sucrase.
I have this working already. I wanted to send the other more straight forward PR first to get a better hang of the process in this project.
from sucrase.
Fixed with #270.
from sucrase.
Related Issues (20)
- How to use sucrase/register/ts with gulpfile.ts? HOT 1
- Dynamic import not act as expected as typescript transpiled HOT 1
- jsx: preserve HOT 2
- TypeScript 5.0 support
- Question: strict mode HOT 2
- Add option to disable TS import/export elision
- Allow arbitrary Sucrase configuration in sucrase/register and the CLI HOT 1
- Transpilation bug, changes `;` to `,` HOT 2
- Constructor return type annotations produce invalid JS syntax HOT 1
- (plugin commonjs--resolver) Syntax Error when importing file with json import HOT 1
- TypeScript: `x < y >= z` is incorrectly interpreted as a type argument list HOT 1
- Incorrect elision of `import {}` with TS transform disabled HOT 1
- TypeScript type-only re-exports not always properly elided
- TypeScript automatic named export elision incorrectly happens for re-export
- Incorrect elision of named import if typings of a callback function contains a parameter with the same name HOT 1
- Sucrase SyntaxError - (7:3) HOT 2
- jest.mock hoisting breaks when using @jest/globals
- Option to just compile JSX to object literal HOT 2
- Unexpected output from an exported mergeable enum HOT 2
- glob lib dependency, depends on Inflight lib which is now introducing a security vulnerability HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sucrase.