-
Notifications
You must be signed in to change notification settings - Fork 736
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
feat: a better tsconfig.json
#512
Conversation
🦋 Changeset detectedLatest commit: f02e87a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/1881606446/npm-package-wrangler-512 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/512/npm-package-wrangler-512 Or you can use npx https://prerelease-registry.developers.workers.dev/runs/1881606446/npm-package-wrangler-512 dev path/to/script.js |
fs.readFileSync("./tsconfig.json", "utf-8") | ||
); | ||
// tsconfig.json isn't necessarily valid json, so let's use eval to parse it | ||
const tsconfigJson = eval( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can use:
import {parseConfigFileTextToJson} from "typescript";
...
parseConfigFileTextToJson("./tsconfig.json", fs.readFileSync("./tsconfig.json", "utf-8"));
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I considered it... heck why not. changing.
fs.readFileSync("./tsconfig.json", "utf-8") | ||
); | ||
// tsconfig.json isn't necessarily valid json, so let's use eval to parse it | ||
const tsconfigJson = eval( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can use:
import {parseConfigFileTextToJson} from "typescript";
...
parseConfigFileTextToJson("./tsconfig.json", fs.readFileSync("./tsconfig.json", "utf-8"));
f70ae66
to
210f88e
Compare
This makes a better `tsconfig.json` when using `wrangler init`. Of note, it takes the default `tsconfig.json` generated by `tsc --init`, and adds our modifications.
210f88e
to
f02e87a
Compare
This makes a better
tsconfig.json
when usingwrangler init
. Of note, it takes the defaulttsconfig.json
generated bytsc --init
, and adds our modifications.