Consider some node tooling #20
Comments
|
Adding Babel will also make the eventual move to TypeScript easier 😈 |
slifty
added a commit
that referenced
this issue
Apr 13, 2021
This activates the built in module mode. It's a step in the right ES6 direction without going full-blown babel (see issue #20). Specifically this will allow us to use `import` and `export`
hawkinsw
added a commit
to hawkinsw/SimpleBook
that referenced
this issue
May 1, 2021
1. Slowly begin migrating code to Typescript from raw Javascript 2. Instead of relying on built-in node module bundling, use webpack These are prerequisites (in a very yak-shaving way) for adding unit testing to the code via Jest. See OpenTechStrategies#20.
hawkinsw
added a commit
to hawkinsw/SimpleBook
that referenced
this issue
May 4, 2021
1. Slowly begin migrating code to Typescript from raw Javascript 2. Instead of relying on built-in node module bundling, use webpack These are prerequisites (in a very yak-shaving way) for adding unit testing to the code via Jest. See OpenTechStrategies#20.
hawkinsw
added a commit
to hawkinsw/SimpleBook
that referenced
this issue
May 4, 2021
1. Slowly begin migrating code to Typescript from raw Javascript 2. Instead of relying on built-in node module bundling, use webpack 3. Add a `yarn watch` command that will rebuild mw2pdf when any TS file is edited. These are prerequisites (in a very yak-shaving way) for adding unit testing to the code via Jest. See OpenTechStrategies#20.
hawkinsw
added a commit
to hawkinsw/SimpleBook
that referenced
this issue
May 5, 2021
1. Slowly begin migrating code to Typescript from raw Javascript 2. Instead of relying on built-in node module bundling, use webpack 3. Add a `yarn watch` command that will rebuild mw2pdf when any TS file is edited. These are prerequisites (in a very yak-shaving way) for adding unit testing to the code via Jest. See OpenTechStrategies#20.
hawkinsw
added a commit
to hawkinsw/SimpleBook
that referenced
this issue
May 5, 2021
1. Slowly begin migrating code to Typescript from raw Javascript 2. Instead of relying on built-in node module bundling, use webpack 3. Add a `yarn watch` command that will rebuild mw2pdf when any TS file is edited. These are prerequisites (in a very yak-shaving way) for adding unit testing to the code via Jest. See OpenTechStrategies#20.
hawkinsw
added a commit
to hawkinsw/SimpleBook
that referenced
this issue
May 5, 2021
1. Slowly begin migrating code to Typescript from raw Javascript 2. Instead of relying on built-in node module bundling, use webpack 3. Add a `yarn watch` command that will rebuild mw2pdf when any TS file is edited. These are prerequisites (in a very yak-shaving way) for adding unit testing to the code via Jest. See OpenTechStrategies#20.
hawkinsw
added a commit
to hawkinsw/SimpleBook
that referenced
this issue
May 5, 2021
1. Slowly begin migrating code to Typescript from raw Javascript 2. Instead of relying on built-in node module bundling, use webpack 3. Add a `yarn watch` command that will rebuild mw2pdf when any TS file is edited. These are prerequisites (in a very yak-shaving way) for adding unit testing to the code via Jest. See OpenTechStrategies#20.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Oh node, how we love thee.
In my work on #11 I'm moving the project to
type: "module"which lets us do things likeexport foo()in a utility file.Since it never hurts to move into modern node, I'd like to propose we consider:
Once we do this we can consider adding some CI to invoke the linter + tests before allowing a PR to merge. This will all be especially useful as we consider #18
The text was updated successfully, but these errors were encountered: