goldstack VS svelte-jester

Infrastructure Complexity: Serverless computing emerged as a simplified approach to application development, but the infrastructure it requires can be unexpectedly complex. Tasks like setting up an API gateway with Lambdas can result in extensive configuration, increasing brittleness and the learning curve for developers.

I completed the upgrade and released this in version 0.5.0 of Goldstack.

If you have any question or comments, please reach out or raise an issue 🤗.

Thus, I started the process of developing a server-side rendering friendly template a few months ago. I released this template a while ago and have since also completed the implementation of the new version of my blog. This post contains my experiences and learnings from this process.

For any suggestions, ideas and comments, please be welcome to head to GitHub and create an issue 🤗.

See a full source code example here: lambdaCompression.ts

The above template and boilerplate are regularly updated and automatically tested (project install & standing up infrastructure). If you nonetheless encounter any problems, please raise an issue on GitHub.

Consider helping out making this template better for others by raising an issue in GitHub if you encounter any problems or have questions or ideas.

The above assumes that there is a local .aws/config and/or .aws/credentials file present. Note that the AWS credentials in awsUser can be initialised in many different ways, see the file awsUserUtils.ts for reference or the AWS documentation on Setting SDK Credentials in Node.js.

If you have any comments or ideas for this template, please head over to the Goldstack GitHub project and raise an issue.

svelte-jester: precompiles Svelte components before tests.

I’m using jest with svelte-jester and @testing-library/svelte.

While I mentioned in the beginning of the article that I am relatively happy with the current state of my reference TypeScript monorepo template, I still think there are a couple of things that can be improved. Chiefly I think that Yarn 2 (‘Berry’) is still not as mature as I would like it to be. Support for ESM for instance would be awesome, the lack of which caused me some problems in trying to make Svelte work within the monorepo. However, I think it is very worthwhile what the Yarn team attempts to achieve with Yarn 2 and I am happy to support it by trying to make it work in the monorepo template.

I need to test some components that require svelte-spa-router by using jest. Well the problem is, an import from svelte-spa-router causes the error on my previous successful tests. Came across this kind of issue on github https://github.com/mihar-22/svelte-jester/issues/7 and try to replicate the solution like this.