Transpile all frontity.settings/config imports

[luisherranz]

What:

Change the files that the ts-node that we run in the dev and build commands transpile.

Why:

Because it was not transpiling files that were inside the node_modules folder, like frontity.config.js files in external packages.

How:

I created a regular expression that is passed to the ignores setting of ts-node and makes it transpile only:

• Packages from the @frontity org
• Packages with frontity in the name (for example some-frontity-package).
• frontity.settings files
• frontity.config files
• Any TypeScript files that people import.

By default this setting was node_modules.

This ts-node transpilation is only used outside of Webpack, which means mostly things people import in their frontity.settings or frontity.config files. Once Webpack runs, all the files are transpiled.

Tasks:

• Code
• Unit tests
• Add a changeset (with link to its Feature Discussion if it exists)

Unrelated Tasks

• TSDocs
• TypeScript
• End to end tests
• TypeScript tests
• Update starter themes
• Update other packages
• Update community discussions

[changeset-bot]

🦋 Changeset detected

Latest commit: 039d6fd

The changes in this PR will be included in the next version bump.

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

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[michalczaplinski]

I'm not sure why the CLI tests keep failing occasionally and only on MacOS. I thought this should have been fixed in #824.

[luisherranz]

True. It seems like this time was a timeout. We'll keep an eye on them 🙂

I have rerun them and they passed this time.

[DAreRodz]

Seems just fine to me. 👍

Although for me it's not clear the part of not ignoring packages with frontity. Would it mean that some frontity packages (those imported by frontity settings/config files) should contain frontity in their name?

[luisherranz]

It is a compromise between transpiling everything (which is pretty slow) and not transpiling anything, which could lead to problems like the one this PR is trying to solve. I tried to come up with a set of scenarios where transpiling seems more right than wrong.

EDIT: I think I didn't address your question:

Would it mean that some frontity packages (those imported by frontity settings/config files) should contain frontity in their name?

The answer is no, they don't need to contain frontity in their names for a normal use 🙂