Do imports used in getStaticProps get bundled?

[mrclay]

I want to make sure my getStaticProps code does not end up in JS bundles, and that includes functions called which have to be imported at the page level.

Does using Typescript have any effect?

Do I need to use require() and/or node’s fs.readfileSync to load modules and any API keys inside the gSP function body?

[ljosberinn]

Using typescript has no effect on this and as the docs mention, node code/code included in getStaticProps/getServerSideProps/getStaticPaths does not get bundled client side. You can easily confirm this e.g. if you enable browserSourceMaps: true in next.config.js > experimental and check the resulting source maps, which show any server side code greyed out.

[mrclay]

Thanks! I’ll verify. Again, I understand the gSP() function itself won’t be bundled. Concern is import in the containing module.

[mrclay]

https://next-code-elimination.now.sh/s/yDIpMw_Iw looks like I just need to be careful to avoid combining client and server API exports in the same module(s).

[ljosberinn]

Yes, that is indeed the case, sorry for not intitially mentioning it. I've built something for sentry here which boots only the relevant variant based on environment by passing the correct init function.

As a result, only client and shared show up in the source maps: