SchnWalter

@rafaelfesi, that's for `package.json`, not for the `npmrc` files, which are used to configure NPM. * https://docs.npmjs.com/files/npmrc * https://docs.npmjs.com/misc/config#engine-strict And the configuration works for me: ``` $ cat .npmrc engine-strict=true...

Just search for the entry point name inside the entry point. It's quick and easy. For dependencies between files inside an entry point, you already have the circular dependency graph...

This should either be closed as `won't fix` or we should just throw an explicit error when a file outside the project root is included in the list. If we...

Interesting find. If what you are trying to solve is a performance problem, the approach is not to ignore sub-entry points, because you will run into issues with the dependency...

From what I can tell, `scheduleEntryPoints` is creating a lot of class instances for each entry point. We might be able to reduce the resource usage and the build duration...

Thanks @JoostK. Nice work! The build time for a basic library[1] is down to ~18% of what I saw with the latest version of the master branch. About ~13s instead...

@alan-agius4, could you please review and merge this PR? With the changes from this PR, entry points now have a reference to the parent entry point and it will allow...

Just to add a note, we already have an undocumented support for empty "secondary entry points", which allows us to have a library that skips "one level" in the sub-package...

We can't use the subpath pattern because we have more data in our secondary entry point `package.json` files, and that pattern can't expose such data: ``` # cat package.json {...

This seems to be related to code that isn't exported, and the issue is also present with the latest dependencies. In the linked, if you export `const isValidDate = (str)...