Peter Pistorius

This is my hacky fix to deal with this: in package.json: ```json /* ... */ "scripts: { "i18n:extract": "mv babel.config.js .babelrc.js; yarn babel-node ./bin/extract_i18n.js; mv .babelrc.js babel.config.js" }

:+1:

Nice, I would love to see what a changeset looks like?

Oh, I meant more as a contributor that produces change-sets? Is there anything that I need to do differently?

This is rad, let's get it in!

@chris-hailstorm That's a great solution and probably a lot easier than the route I was suggesting. Another way to do this, for both sides, could be by specifying it as...

Hey @noire-munich, You could modify the netlify build command to also build your package: ```toml [build] command = "NODE_ENV=production yarn rw db up --no-db-client --auto-approve && yarn rw build &&...

@noire-munich That's something that I want to add: In the meantime you could do something like: https://github.com/redwoodjs/redwood/blob/b72db535c84a0656a28d1fa2dd2a9460d3bfd78f/packages/api/package.json#L41

@jangxyz you would have add your "sharing folder" to your paths. So, the first thing I'm seeing is that you're using a relative import. I would modify the `api/babel.config.js` babel...

@jangxyz I think you should only have either `jsconfig.json` or `tsconfig.json`, but not both.